public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bharath Ramesh <krosswindz@gmail.com>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: "Bagalkote, Sreenivas" <Sreenivas.Bagalkote@engenio.com>,
	"Bhattacharjee, Satadal" <Satadal.Bhattacharjee@engenio.com>,
	linux-kernel@vger.kernel.org, "Patro,
	Sumant" <Sumant.Patro@engenio.com>,
	"Ram, Hari" <hari.ram@engenio.com>,
	"Mukker, Atul" <Atul.Mukker@engenio.com>
Subject: Re: Registering for multiple SIGIO within a process
Date: Wed, 28 Sep 2005 23:50:11 -0400	[thread overview]
Message-ID: <c775eb9b0509282050429bd73@mail.gmail.com> (raw)
In-Reply-To: <1127956550.25462.15.camel@orca.madrabbit.org>

On 9/28/05, Ray Lee <ray-lk@madrabbit.org> wrote:
> On Wed, 2005-09-28 at 20:44 -0400, Bagalkote, Sreenivas wrote:
> > >(Sheesh, what is it with people thinking signals are something
> > >to be used in any design after the 1970's?)
> > What's your recommendation for asynchronous notification from driver
> > to an application?
>
> Pass back an fd to select() upon. Cuts out that nasty middle step where
> app authors end up registering a signal handler that merely write()s the
> signal number down a pipe into the (nearly ubiquitous) select loop.

If its just linux i would use asynchronous notification using RT
signals. You can use sigwaitinfo to check for the arrival of the
signal by blocking it. siginfo will contain the fd which receivd the
notification. That saves you the call to select as you would have to
select upto maxfd. If you are using just one fd poll would be a better
option IMHO.


Bharath

  reply	other threads:[~2005-09-29  3:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  0:44 Registering for multiple SIGIO within a process Bagalkote, Sreenivas
2005-09-29  1:15 ` Ray Lee
2005-09-29  3:50   ` Bharath Ramesh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-29  4:09 Bagalkote, Sreenivas
2005-09-29  5:28 ` Ray Lee
2005-09-28 22:02 Bhattacharjee, Satadal
2005-09-28 22:51 ` Ray Lee
2005-09-28 23:08 ` Bharath Ramesh

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=c775eb9b0509282050429bd73@mail.gmail.com \
    --to=krosswindz@gmail.com \
    --cc=Atul.Mukker@engenio.com \
    --cc=Satadal.Bhattacharjee@engenio.com \
    --cc=Sreenivas.Bagalkote@engenio.com \
    --cc=Sumant.Patro@engenio.com \
    --cc=hari.ram@engenio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox