More about performance.

[bmusb] / README

diff --git a/README b/README
index e5fb92cb72811e0a9c022346802479a09a7bfa8f..d26ca1223e3817bac3960885a8bcf77c41be3f59 100644 (file)
--- a/README
+++ b/README
@@ -17,8 +17,12 @@ ABI stability, for one, and everything is really messy and uncommented.)
 In particular, it will often do something on init that makes the card
 seemingly reset and disconnect off the bus (and then reset).
 This being said, once it's actually up, I've done ten-hour 720p60
-captures on my Lenovo X240 without a single drop. It seems to want about
-10–15% of one CPU core.
+captures on my Lenovo X240 without a single drop.
+
+It seems to want about 10–15% of one CPU core; a significant chunk of this is
+copying data from the kernel over to userspace. However, it supports custom
+memory allocators, so that once the USB packets are in userspace, you can
+decode directly into e.g. pinned GPU memory.
 
 The driver itself lives in bmusb.cpp; main.cpp contains a very simple
 client that just checks for frame continuity. It's recommended to run