RE: WaitForMultipleObjects/etc. In Kernel

2014-01-31 Thread Network Nut
> -Original Message- > From: Network Nut [mailto:sillyst...@gmail.com] > Sent: Friday, January 31, 2014 5:00 PM > To: 'Clemens Ladisch' > Cc: 'Austin S. Hemmelgarn'; linux-kernel@vger.kernel.org > Subject: RE: WaitForMultipleObjects/etc. In Kernel > > -Origin

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-31 Thread Network Nut
> -Original Message- > From: Clemens Ladisch [mailto:clem...@ladisch.de] > Sent: Friday, January 31, 2014 4:54 PM > To: Network Nut > Cc: 'Austin S. Hemmelgarn'; linux-kernel@vger.kernel.org > Subject: Re: WaitForMultipleObjects/etc. In Kernel > > Network

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-31 Thread Network Nut
> -Original Message- > From: Austin S. Hemmelgarn [mailto:ahferro...@gmail.com] > Sent: Friday, January 31, 2014 11:05 AM > To: Network Nut; 'Clemens Ladisch' > Cc: linux-kernel@vger.kernel.org > Subject: Re: WaitForMultipleObjects/etc. In Kernel > >> Network Nu

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-31 Thread Network Nut
-Original Message- From: Austin S. Hemmelgarn [mailto:ahferro...@gmail.com] Sent: Friday, January 31, 2014 11:05 AM To: Network Nut; 'Clemens Ladisch' Cc: linux-kernel@vger.kernel.org Subject: Re: WaitForMultipleObjects/etc. In Kernel Network Nut wrote: I was thinking

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-31 Thread Network Nut
-Original Message- From: Clemens Ladisch [mailto:clem...@ladisch.de] Sent: Friday, January 31, 2014 4:54 PM To: Network Nut Cc: 'Austin S. Hemmelgarn'; linux-kernel@vger.kernel.org Subject: Re: WaitForMultipleObjects/etc. In Kernel Network Nut wrote: Assuming that you're

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-31 Thread Network Nut
-Original Message- From: Network Nut [mailto:sillyst...@gmail.com] Sent: Friday, January 31, 2014 5:00 PM To: 'Clemens Ladisch' Cc: 'Austin S. Hemmelgarn'; linux-kernel@vger.kernel.org Subject: RE: WaitForMultipleObjects/etc. In Kernel -Original Message- From: Clemens

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-30 Thread Network Nut
> -Original Message- > From: Clemens Ladisch [mailto:clem...@ladisch.de] > Sent: Wednesday, January 29, 2014 2:31 AM > To: Network Nut > Cc: linux-kernel@vger.kernel.org > Subject: RE: WaitForMultipleObjects/etc. In Kernel > > Network Nut wrote: > >I was look

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-30 Thread Network Nut
-Original Message- From: Clemens Ladisch [mailto:clem...@ladisch.de] Sent: Wednesday, January 29, 2014 2:31 AM To: Network Nut Cc: linux-kernel@vger.kernel.org Subject: RE: WaitForMultipleObjects/etc. In Kernel Network Nut wrote: I was looking at POSIX because it allows naming

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-28 Thread Network Nut
> -Original Message- > From: Clemens Ladisch [mailto:clem...@ladisch.de] > Sent: Tuesday, January 28, 2014 3:04 AM > To: Network Nut > Cc: linux-kernel@vger.kernel.org > Subject: Re: WaitForMultipleObjects/etc. In Kernel > > Network Nut wrote: > > 5. I ca

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-28 Thread Network Nut
-Original Message- From: Clemens Ladisch [mailto:clem...@ladisch.de] Sent: Tuesday, January 28, 2014 3:04 AM To: Network Nut Cc: linux-kernel@vger.kernel.org Subject: Re: WaitForMultipleObjects/etc. In Kernel Network Nut wrote: 5. I can simulate system-global named mutex using

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-27 Thread Network Nut
> Unrelated processes cannot directly open objects created by another > process (with the exception of sockets and pipes, which can be created in > the file system). However, sharing of any file descriptor is possible by > sending it in a control message through a Unix domain socket. I just

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-27 Thread Network Nut
Unrelated processes cannot directly open objects created by another process (with the exception of sockets and pipes, which can be created in the file system). However, sharing of any file descriptor is possible by sending it in a control message through a Unix domain socket. I just spent a

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-26 Thread Network Nut
> -Original Message- > From: Clemens Ladisch [mailto:clem...@ladisch.de] > Sent: Sunday, January 26, 2014 12:33 PM > To: Network Nut > Cc: linux-kernel@vger.kernel.org > Subject: Re: WaitForMultipleObjects/etc. In Kernel > > Network Nut wrote: > > I th

RE: WaitForMultipleObjects/etc. In Kernel

2014-01-26 Thread Network Nut
-Original Message- From: Clemens Ladisch [mailto:clem...@ladisch.de] Sent: Sunday, January 26, 2014 12:33 PM To: Network Nut Cc: linux-kernel@vger.kernel.org Subject: Re: WaitForMultipleObjects/etc. In Kernel Network Nut wrote: I think that the facility by which a thread can

WaitForMultipleObjects/etc. In Kernel

2014-01-25 Thread Network Nut
Hi All, This is my first post to anything Linux, so if there is a better mailing list, please let me know. I think that the facility by which a thread can block while waiting for any of several synchronization primitives (*mutex*, *semaphore*, *event*, *waitable timer*)...is not only "nice to

WaitForMultipleObjects/etc. In Kernel

2014-01-25 Thread Network Nut
Hi All, This is my first post to anything Linux, so if there is a better mailing list, please let me know. I think that the facility by which a thread can block while waiting for any of several synchronization primitives (*mutex*, *semaphore*, *event*, *waitable timer*)...is not only nice to