From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
Davide Libenzi <davidel@xmailserver.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Synchronous signal delivery..
Date: Fri, 14 Feb 2003 20:30:05 -0500 [thread overview]
Message-ID: <3E4D981D.209@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302141704280.1296-100000@penguin.transmeta.com>
Linus Torvalds wrote:
> On Sat, 15 Feb 2003, Matti Aarnio wrote:
>
>>Do we need new syscall(s) ? Could it all be done with netlink ?
>
>
> We'd need the same new system call - the one to associate signals of this
> process with the netlink thing.
>
> (Yeah, the "system call" could be an ioctl entry, but quite frankly,
> that's much WORSE than adding a system call. It's just system calls
> without type checking).
I have been lobbying for sys_garzik(2) for years... while you're in
there adding stuff, can you slip that in too please?
... :)
More seriously, and a bit of a tangent, I wonder how much attention we
need to give netlink. Because it either has the potential to be used as
a de facto in-kernel event-passing API, or it's too heavyweight for
that, implying [IMO] we need a netlink-lite.
I _don't_ want to see mini-netlinks springing up every time we need
[a]sync <foo> delivery inside the kernel.
Jeff
next prev parent reply other threads:[~2003-02-15 1:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 19:46 Synchronous signal delivery Linus Torvalds
2003-02-13 20:22 ` Davide Libenzi
2003-02-13 20:25 ` Linus Torvalds
2003-02-13 22:26 ` Davide Libenzi
2003-02-13 22:54 ` Linus Torvalds
2003-02-14 8:55 ` Abramo Bagnara
2003-02-14 14:24 ` Alan Cox
2003-02-14 13:57 ` Abramo Bagnara
2003-02-15 12:36 ` Ingo Oeser
2003-02-15 17:59 ` Abramo Bagnara
2003-02-16 14:52 ` Ingo Oeser
2003-02-15 0:00 ` Davide Libenzi
2003-02-15 0:06 ` Matti Aarnio
2003-02-15 1:08 ` Linus Torvalds
2003-02-15 1:30 ` Jeff Garzik [this message]
2003-02-15 1:23 ` Davide Libenzi
2003-02-15 1:03 ` Linus Torvalds
2003-02-15 2:09 ` Davide Libenzi
2003-02-15 20:08 ` Linus Torvalds
2003-02-15 23:39 ` Davide Libenzi
2003-02-17 2:28 ` Jan Harkes
2003-02-15 5:04 ` Keith Adamson
2003-02-15 19:19 ` James Antill
2003-02-15 22:31 ` Davide Libenzi
2003-02-17 23:34 ` James Antill
2003-02-17 15:26 ` Daniel Heater
2003-02-15 4:08 ` Werner Almesberger
2003-02-15 22:00 ` Davide Libenzi
2003-02-16 0:18 ` Werner Almesberger
2003-02-17 4:46 ` Jamie Lokier
2003-02-13 20:45 ` Paul P Komkoff Jr
2003-02-13 21:25 ` Richard B. Johnson
2003-03-27 21:40 ` watching for file creation completion [was Re: Synchronous signal delivery..] Alexander Kellett
2003-02-14 2:40 ` Synchronous signal delivery Jamie Lokier
2003-02-14 3:11 ` Keith Adamson
2003-02-14 3:54 ` Keith Adamson
2003-02-15 0:04 ` Davide Libenzi
2003-02-15 1:01 ` Jamie Lokier
2003-02-15 1:12 ` Randy.Dunlap
2003-02-15 1:50 ` Davide Libenzi
2003-02-15 2:08 ` Jamie Lokier
2003-02-15 4:09 ` Davide Libenzi
2003-02-15 4:34 ` Jamie Lokier
2003-02-14 10:55 ` Giuliano Pochini
2003-02-14 13:04 ` Keith Adamson
2003-02-15 4:25 ` Werner Almesberger
2003-02-15 5:14 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 7:09 Dan Kegel
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=3E4D981D.209@pobox.com \
--to=jgarzik@pobox.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=torvalds@transmeta.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