Messages in this thread | | | From | Daniel Phillips <> | Subject | Re: GFS requirements (was: Non-GPL export of invalidate_mmap_range) | Date | Tue, 24 Feb 2004 13:26:04 -0500 |
| |
On Sunday 22 February 2004 05:37, Lars Marowsky-Bree wrote: > > > So, how does OpenGFS/GFS achieve the communication? How does it > > > interact with the infrastructure (which, I infere from your above > > > comments, is meant to reside in user-space)? > > > > It's done both ways, actually. No new kernel hooks are used in either > > case. > > That doesn't answer my question how you are doing the user-space / > kernel communication ;-)
Hi Lars,
OpenGFS uses sockets, see:
http://cvs.sourceforge.net/viewcvs.py/opengfs/opengfs/src/locking/modules/memexp/moduleops.c?view=markup
> And will the user-space infrastructure to go with GFS be open source > too? Questions over questions.
Yes, it's all to be opened up. If you don't mind, I'd prefer to hold off discussing the infrastructure details until the code lands.
Regards,
Daniel
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |