Maybe "system management" is a good description. I'm considering writing a USB Mass Storage gadget. It will be necessary somehow to connect the gadget to an underlying storage medium, and the simplest approach seems to be the one used by the loop driver. That is, an ioctl call provides the gadget driver with a descriptor for a block device or a regular file, which the driver then uses. (Also, that means I can just copy the loop driver code :-)
Is there a need for this to be in kernel space at all? If the reason is performance, wouldn't knfsd be the model to look at?
I'd put it in the kernel since the folk who've been most interested in having such gadgets need the performance ... they're using embedded processors, not all of which have the oomph of a 486/66.
I'm not sure what the right model would be, myself ... iSCSI servers, perhaps.
- Dave
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
