All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Antill <james@and.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Synchronous signal delivery..
Date: 17 Feb 2003 18:34:39 -0500	[thread overview]
Message-ID: <m3smumfpm8.fsf@code.and.org> (raw)
In-Reply-To: <Pine.LNX.4.50.0302151430230.1891-100000@blue1.dev.mcafeelabs.com>

Davide Libenzi <davidel@xmailserver.org> writes:

> On Sat, 15 Feb 2003, James Antill wrote:
> 
> > > I would personally like it a lot to have timer events available on
> > > pollable fds. Am I alone in this ?
> >
> >  Think of "timer events" as a single TCP connection, so you have...
> 
> I'm sorry, I'm a bit confused. What's the point here ?

 Just that although you could have each timer event on separate
pollable fds it's much the same as having separate events for 1
byte, 2 bytes, and 4 bytes available on a network socket (Ie. you are
much better off keeping that all in user space).

-- 
# James Antill -- james@and.org
:0:
* ^From: .*james@and\.org
/dev/null

  reply	other threads:[~2003-02-17 23:26 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
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 [this message]
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=m3smumfpm8.fsf@code.and.org \
    --to=james@and.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.