From: Christopher Smith <x@xman.org>
To: "Dan Maas" <dmaas@dcine.com>, "John Fremlin" <vii@users.sourceforge.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: A signal fairy tale
Date: Fri, 29 Jun 2001 01:26:29 -0700 [thread overview]
Message-ID: <5.1.0.14.0.20010629012354.02b759d0@imap.xman.org> (raw)
In-Reply-To: <00b101c0ffe2$fb77ad30$0701a8c0@morph>
In-Reply-To: <fa.d69j5vv.ej8irj@ifi.uio.no> <fa.h2rpibv.87m5bp@ifi.uio.no>
At 10:59 AM 6/28/2001 -0400, Dan Maas wrote:
>life-threatening things like SIGTERM, SIGKILL, and SIGSEGV. The mutation
>into queued, information-carrying siginfo signals just shows how badly we
>need a more robust event model... (what would truly kick butt is a unified
>interface that could deliver everything from fd events to AIO completions to
>semaphore/msgqueue events, etc, with explicit binding between event queues
>and threads).
I guess this is my thinking: it's really not that much of a stretch to make
signals behave like GetMessage(). Indeed, sigopen() brings them
sufficiently close. By doing this, you DO provide this unified interface
for all the different types of events you described which works much like
GetMessage(). So, but adding a couple of syscalls you avoid having to
implement a whole new set of API's for doing AIO, semaphores, msgqueues, etc.
--Chris
P.S.: What do you mean by explicit binding between event queues and
threads? I'm not sure I see what this gains you.
next prev parent reply other threads:[~2001-06-29 8:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.d69j5vv.ej8irj@ifi.uio.no>
[not found] ` <fa.h2rpibv.87m5bp@ifi.uio.no>
2001-06-28 14:59 ` Dan Maas
2001-06-28 15:21 ` Alan Cox
2001-06-29 8:26 ` Christopher Smith [this message]
2001-06-29 11:56 ` Chris Wedgwood
2001-06-30 10:02 ` Jan Hudec
2001-06-28 20:11 Daniel R. Kegel
2001-06-29 8:31 ` Christopher Smith
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 3:04 Daniel R. Kegel
2001-06-28 14:46 ` Jamie Lokier
2001-06-28 2:57 Daniel R. Kegel
2001-06-29 8:19 ` Christopher Smith
2001-06-29 9:29 ` Dan Kegel
2001-06-29 18:46 ` Dan Kegel
2001-07-02 22:33 ` Christopher Smith
2001-06-28 2:49 Daniel R. Kegel
2001-06-29 8:18 ` Christopher Smith
2001-06-29 9:05 ` Dan Kegel
2001-06-26 12:54 Dan Kegel
2001-06-27 3:56 ` Christopher Smith
2001-06-27 6:21 ` Balbir Singh
2001-06-27 18:11 ` Christopher Smith
2001-06-28 3:28 ` Balbir Singh
2001-06-27 9:18 ` Jamie Lokier
2001-06-27 18:16 ` Christopher Smith
2001-06-28 12:58 ` John Fremlin
2001-06-28 16:21 ` Jamie Lokier
2001-06-29 8:22 ` Christopher Smith
2001-06-29 11:47 ` John Fremlin
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=5.1.0.14.0.20010629012354.02b759d0@imap.xman.org \
--to=x@xman.org \
--cc=dmaas@dcine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vii@users.sourceforge.net \
/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
all inboxes | Powered by JetHome®