mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, sct@redhat.com
Subject: Re: [patch rfc] towards supporting O_NONBLOCK on regular files
Date: Wed, 13 Oct 2004 10:28:49 -0400	[thread overview]
Message-ID: <16749.15265.475571.767534@segfault.boston.redhat.com> (raw)
In-Reply-To: <20041003194831.GB3089@openzaurus.ucw.cz>

==> Regarding Re: [patch rfc] towards supporting O_NONBLOCK on regular files; Pavel Machek <pavel@ucw.cz> adds:

pavel> Hi!
>> This patch makes an attempt at supporting the O_NONBLOCK flag for
>> regular files.  It's pretty straight-forward.  One limitation is that we
>> still call into the readahead code, which I believe can block.  However,
>> if we don't do this, then an application which only uses non-blocking
>> reads may never get it's data.

pavel> This looks very nice. Does it mean that aio and friends are
pavel> instantly obsolete?

I dont' think so.  This only addresses the read() path, for one.  Plus, in
it's current form, it will not perform any I/O if the data is not present.
So, you will need another thread/process to do kick off the I/O.

pavel> Does it have comparable performance to aio?

I haven't run any tests.  One advantage this has to current aio is that it
can operate without O_DIRECT.

-Jeff

  reply	other threads:[~2004-10-13 14:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 20:57 Jeff Moyer
2004-10-03 19:48 ` Pavel Machek
2004-10-13 14:28   ` Jeff Moyer [this message]
2004-10-14 17:39     ` Pavel Machek
2004-10-05 11:27 ` Marcelo Tosatti
2004-10-06 13:13   ` Jeff Moyer
2004-10-06 12:01     ` Marcelo Tosatti
2004-10-07  3:31       ` Stephen C. Tweedie
2004-10-07 10:12         ` Marcelo Tosatti
2004-10-07 12:30           ` Arjan van de Ven
2004-10-11 18:32           ` Stephen C. Tweedie
2004-10-11 18:58             ` Jeff Moyer
2004-10-11 21:49               ` Stephen C. Tweedie
2004-10-13 14:26                 ` Jeff Moyer
2004-10-15 15:44                   ` Jeff Moyer
2004-10-15 16:19                     ` Stephen C. Tweedie
2004-10-17  7:59                     ` Alexandre Oliva
2004-10-17 11:20                       ` Ingo Molnar
2004-10-17 19:38                         ` Alexandre Oliva
2004-10-18 16:51                           ` Jeff Moyer
2004-10-19  6:04                             ` Alexandre Oliva
2004-10-21 20:14                             ` James Antill
2004-10-05 15:35 ` Rik van Riel
2004-10-05 13:07 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=16749.15265.475571.767534@segfault.boston.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=sct@redhat.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®