>> Ok, urandom was a bad example. I have my tty logger (ttyrpld.sf.net) which >> moves a lot of data (depends) to userspace. It uses a ring buffer [...] >[...] >Basically, all the transport code you are doing in the kernel side of >your logger would be taken care of by relayfs. And given that there are >a lot of people doing similar ad-hoc buffering code, it just makes >sense to have one well-tested yet generic mechanism. Have a look at >Documentation/filesystems/relayfs.txt for the API details.
Well, what about things like urandom? It also moves "a lot" of data and does nothing else. >[...] >Just to avoid any confusion, note that I'm referring mainly to rpldev.c, >which is the kernel-side driver for the logger, I haven't looked at any >of the user tools. The userspace daemon just read()s the device and analyzes it. Nothing to optimize there, with respect to relayfs, I think. Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/