mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amos Waterland <apw@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Cc: Tom Gall <tom_gall@vnet.ibm.com>
Subject: Re: O_ASYNC question
Date: Wed, 26 Jun 2002 16:37:55 -0500	[thread overview]
Message-ID: <20020626163755.A10713@kvasir.austin.ibm.com> (raw)
In-Reply-To: <20020626211122.GL22961@holomorphy.com>; from wli@holomorphy.com on Wed, Jun 26, 2002 at 02:11:22PM -0700

On Wed, Jun 26, 2002 at 02:11:22PM -0700, William Lee Irwin III wrote:
> On Tue, Jun 25, 2002 at 11:30:52AM -0500, Amos Waterland wrote:
> > The man page for fcntl() says:
> >     If you set the O_ASYNC status flag on a file descriptor (either by
> >     providing this flag with the open(2) call, or by using the F_SETFL
> >     command of fcntl), a SIGIO signal is sent whenever input or output
> >     becomes possible on that file descriptor.
> 
> Not done for files and you need fsetown() for sockets and tty's.

Thanks for the reply.

The reason that I was interested is that this behavior, if implemented
for all fd types, would be useful for a scalable user-space
implementation of POSIX aio.

When you say that it is 'not done for files', does that mean that it is
not done by design, and no plans exist to implement it for files
(perhaps because completion notification is fundamentally different than
readiness notification?), or that the work just has yet to be done?
Thanks.

Amos W.

  reply	other threads:[~2002-06-26 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 16:30 Amos Waterland
2002-06-26 21:11 ` William Lee Irwin III
2002-06-26 21:37   ` Amos Waterland [this message]
2002-06-27  0:56     ` William Lee Irwin III
2002-06-27 12:15     ` Jamie Lokier
2006-11-10 22:57 Mikulas Patocka

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=20020626163755.A10713@kvasir.austin.ibm.com \
    --to=apw@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom_gall@vnet.ibm.com \
    --cc=wli@holomorphy.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

all inboxes | Powered by JetHome®