From: Clemens Ladisch <clemens@ladisch.de>
To: Network Nut <sillystack@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WaitForMultipleObjects/etc. In Kernel
Date: Mon, 27 Jan 2014 10:06:34 +0100 [thread overview]
Message-ID: <52E6219A.3020405@ladisch.de> (raw)
In-Reply-To: <012d01cf1ae3$6543e340$2fcba9c0$@gmail.com>
Network Nut wrote:
> As you know, under Windows, synchronization objects such as {event | mutex |
> semaphore | timer}; all have names that are computer-global. Process B can
> open, and use, any {event | mutex | semaphore | timer} that was created by
> process A, as long as Process B knows the name that was used by Process A to
> create the {event | mutex | semaphore | timer}. [...]
> Is there a method I can use where Process A and Process B can both refer to
> the same eventfd by name?
In Unix, the most common method of sharing file descriptors is by
letting child processes inherit them. (This also works in Windows, but
is not as efficient due to the process creation overhead.)
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.
> BTW, the man page for epoll_wait seems to be incorrect.
<https://www.kernel.org/doc/man-pages/reporting_bugs.html>
> "The timeout argument specifies the minimum number of milliseconds
> that epoll_wait() will block."
>
> I think the word "minimum" should be "maximum".
This sentence was copied from the poll(2) man page, where the previous
sentence says "poll() blocks until one of the events occurs". So the
word "block" implies that no event has occured.
Regards,
Clemens
next prev parent reply other threads:[~2014-01-27 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 22:01 WaitForMultipleObjects/etc. In Kernel Network Nut
2014-01-26 18:33 ` Clemens Ladisch
2014-01-26 22:10 ` Network Nut
2014-01-27 9:06 ` Clemens Ladisch [this message]
2014-01-27 19:50 ` Network Nut
2014-01-28 9:04 ` Clemens Ladisch
2014-01-28 21:07 ` Network Nut
2014-01-29 8:30 ` Clemens Ladisch
2014-01-30 23:49 ` Network Nut
2014-01-31 17:05 ` Austin S. Hemmelgarn
2014-01-31 22:35 ` Network Nut
2014-01-31 22:53 ` Clemens Ladisch
2014-01-31 23:00 ` Network Nut
2014-01-31 23:08 ` Network Nut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E6219A.3020405@ladisch.de \
--to=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sillystack@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox