From: Abramo Bagnara <abramo.bagnara@libero.it>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>,
Davide Libenzi <davidel@xmailserver.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Synchronous signal delivery..
Date: Sat, 15 Feb 2003 18:59:47 +0100 [thread overview]
Message-ID: <3E4E8013.C26DFA0@libero.it> (raw)
In-Reply-To: 20030215133600.F629@nightmaster.csn.tu-chemnitz.de
Ingo Oeser wrote:
>
> On Fri, Feb 14, 2003 at 02:57:38PM +0100, Abramo Bagnara wrote:
> > > Out of band data is a second data channel, so open two pipes. Jeez
> >
> > What about the relation between the two channels?
>
> Encoded in the program logic, where it belongs. We have enough
> needless interrelations between API functions already.
>
> If you would like to have two channels in one, than simply
> implement a multiplexer in the program that needs it (look at ssh
> for an example).
We might call this thread "the neverending misunderstanding" ;-)
My message was a proposal about an universal solution for
control/out-of-band streams on pseudo-files (like the Linus sig fd,
devices fd, socket, proc files, etc.) as a way to comunicate between
user space and kernel space.
I.e. something that might replace ioctl/fcntl mess giving same (and
more) flexybility and power (extending the 'everything is a file'
concept also to control data).
This is *not* something I'd propose for user space (where we definitely
have many good ways to achieve these results).
--
Abramo Bagnara mailto:abramo.bagnara@libero.it
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
next prev parent reply other threads:[~2003-02-15 17:58 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 [this message]
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
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=3E4E8013.C26DFA0@libero.it \
--to=abramo.bagnara@libero.it \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidel@xmailserver.org \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.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