On Tue, Jul 31, 2007 at 10:10:05AM +0300, Gilad Ben-Yossef wrote: > Anyway, you're doing the right thing. Just supply a userspace > library that wraps the /dev, /proc or your new file virtual system > operation for the user amnd implement you "system call" as a library > function in it. > > Later, when/if your new system call will get accepted into the > mainline kernel and integrated into glibc and friends he interface > can remain the same for the application, modulo not requiring your > interface library.
This approach is potentially problematic, We've had bad experiences with this approach, e.g., with libsysfs, but we've also had good experiences with it, e.g., with the IB verbs libraries. The really right thing to do is to get the system call upstream first, if at all possible... On the other hand, if you're just doing an in-house thing where the kernel module and the application matters, it doesn't matter very much, except getting it upstream should cut your maintenance costs over the long run by orders of magnitude. Cheers, Muli ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
