Messages in this thread | | | Date | Sun, 20 Jan 2008 02:29:34 +0100 | From | Jan-Benedict Glaw <> | Subject | Re: new file in kernel. |
| |
On Sat, 2008-01-19 12:12:10 -0300, Rafael Sisto <rafael.sisto@gmail.com> wrote: > Dear Jan, > > The idea of the indirection is to make it transparent for the user. > The idea is to do almost the same as what IPC does. The user calls > "get", then "attach". In the "get" syscall I create a tmp file and > return some id. Then the user calls an "attach" syscall with the > returned id. > > The result is that he gets a shared memorymapped to his vma.
So my understanding is that you want to get a "IPC shared memory for dummies" API. You're already willing to use custom-numbered system calls, requiring to recompile the Linux kernel, having to add these system calls to libc (or putting _syscallX macros into the application's code) and loosing all portability for the application using this API.
My point of view is that this is a planed nightmare :)
I'd suggest to dig into "Unix Network Programming, Volume 2. Interprocess Communications" and implement that API as a library instead of using a set of new kernel system calls. That way, the applications using it will use that API and only that. They won't require operatins system specific modifications afterwards. OTOH, this library will probably quite portable by itself and shouldn't need any kernel changes, independent of the underlying kernel.
MfG, JBG
-- Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481 Signature of: http://perl.plover.com/Questions.html the second : [unhandled content-type:application/pgp-signature] | |