This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: shm status
- From: "Robert Collins" <robert dot collins at syncretize dot net>
- To: "'Conrad Scott'" <Conrad dot Scott at dsl dot pipex dot com>,<cygwin-developers at cygwin dot com>
- Date: Mon, 10 Jun 2002 01:47:54 +1000
- Subject: RE: shm status
> -----Original Message-----
> From: cygwin-developers-owner@cygwin.com
> [mailto:cygwin-developers-owner@cygwin.com] On Behalf Of Conrad Scott
> Sent: Sunday, 9 June 2002 11:21 PM
> To: cygwin-developers@cygwin.com
> Subject: shm status
>
>
> In message
> http://cygwin.com/ml/cygwin-developers/2002-03/msg00000.html
> "sysV IPC and SHM", Robert Collins announced the availability
> of an initial
> cut of the sysv shm code in cygwin and provided a small test suite
> (ipctest-0.1.2).
>
> First, just to report that I've compiled and run the test
> suite (apparently
> successfully) on my w2k box with the latest cvs cygwin. And
> I've also got
> cygserver running all the time with no apparent problem.
Cool.
> Second, is anyone working actively on the shm implementation
> right now? I
> was going to write some more test cases but, looking at the
> code, I notice
> that it has the odd one or two FIXME comments, so I thought
> it might be
> better to fix those first before trying to find any more issues.
Actively hacking, no. Due to RL time constraints. Feel free to dig in
and submit patches, I do have time to review stuff.
> Also the ipcs and ipcrm utitilities are really useful when
> working with sysv
> ipc so I also thought I could start by adding these.
> Presumably this would
> be a case for another cygwin_internal() interface? i.e. get
> the list of ids;
> the program then issues xxxctl() calls to get the relevant
> details or rm the
> requested objects. Any objections to such an approach? (Just
> for comparison,
> the usual Un*x implementation involves reading kernel memory
> via /dev/kmem.)
Sounds good to me.
Rob