On Sun, Feb 20, 2000 at 07:17:17PM +0100, Marc Mutz wrote:
> Since de/encryption is done in kernel space, these routines eat all of
> the CPU time they can get. I also don't think they are at all scheduled,
> so the time that scheduler has control of, so to speak, is limted. Too
> limited to call xmms thread that writes to /dev/dsp often enough.
Ah, like that. Makes sense I guess. Hmmm, maybe having a userspace worker
thread (mlockall()d, ofcourse), would be a nice idea. Oh well, I wanted to
learn kernel programming anyway.... :-)
--Frank v Waveren fvw@var.cx ICQ# 10074100
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:25 EST