LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: lkv@isg.de
To: "Kernel, Linux" <linux-kernel@vger.kernel.org>
Subject: Desperately missing a working "pselect()" or similar...
Date: Fri, 05 Oct 2001 17:36:29 +0200 [thread overview]
Message-ID: <3BBDD37D.56D7B359@isg.de> (raw)
Hi,
I'm currently looking for a decent method to wait on either
an I/O event _or_ a signal coming from another process.
Alas, it seems that the Linux kernel does not have any
appropriate system call to support what for example "pselect()"
tries to do: Atomically enable some signals and entering a
select.
Without a proper pselect() implementation (the one in glibc is just
a mock-up that doesn't prevent the race condition) I'm currently
unable to come up with a good idea on how to wait on both types
of events.
A somewhat bizarre solution would be to have the process create
a pipe-pair, select on the reading end, and let the signal-handler
write a byte to the pipe - but this has at least the drawback
you always spoil one "select-cycle" for each signal you get - as
the first return from the select() call happenes without any
fds being flagged as readable, only when you enter select() once
more the pipe will cause the return and tell you what happened...
Arguments against other options I considered:
- Using just signals is at least prevented by SIGIO not being
delivered for pipes, and I'm not eager to find out about
all the other problems that may arise by devices not behaving
as expected
- Unix domain sockets would be awkward to use due to the fact
I'd need to come up with some "filenames" for them to bind to,
and both security considerations and the danger of "leaking"
files that remain on disk forever make me shudder...
Any ideas?
Anyone capable of implementing a system-call for pselect() (or ppoll) ?
Regards,
Lutz Vieweg
--
Dipl. Phys. Lutz Vieweg | email: lkv@isg.de
Innovative Software AG | Phone/Fax: +49-69-505030 -120/-505
Feuerbachstrasse 26-32 | http://www.isg.de/people/lkv/
60325 Frankfurt am Main | ^^^ PGP key available here ^^^
next reply other threads:[~2001-10-05 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 15:36 lkv [this message]
2001-10-05 16:19 ` Alexander Viro
2001-10-05 16:28 ` lkv
2001-10-05 16:36 ` Christopher Friesen
2001-10-05 16:40 ` lkv
2001-10-05 20:37 ` Bernd Eckenfels
2001-10-05 23:05 ` Alex Pennace
2001-10-05 23:13 ` Alan Cox
2001-10-05 23:52 ` Alex Pennace
2001-10-05 23:22 ` Neil Brown
2001-10-05 23:30 ` Alex Pennace
2001-10-05 23:43 ` David Schwartz
2001-10-06 0:03 ` Alan Cox
2001-10-08 16:32 lkv
2001-10-08 16:44 ` Alan Cox
2001-10-08 17:06 ` lkv
2001-10-08 17:24 ` Alan Cox
2001-10-09 13:37 ` Jan Hudec
2001-10-13 16:05 ` Jamie Lokier
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=3BBDD37D.56D7B359@isg.de \
--to=lkv@isg.de \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: Desperately missing a working "pselect()" or similar...' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).