From: Mike Hayward <hayward@loup.net>
To: jmoyer@redhat.com
Cc: mvds.00@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: O_NONBLOCK is NOOP on block devices
Date: Fri, 5 Mar 2010 12:43:54 -0700 [thread overview]
Message-ID: <201003051943.o25Jhs6w012994@alien.loup.net> (raw)
In-Reply-To: <x49sk8ezrfq.fsf@segfault.boston.devel.redhat.com> (message from Jeff Moyer on Fri, 05 Mar 2010 11:03:37 -0500)
Hi Jeff,
> I guess I should note that I've suggested nonblocking I/O for files
> before:
>
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-10/0290.html
>
> I'll also note that enabling such a patch broke apps that accessed cd
> burners, for example, since O_NONBLOCK had some preexisting semantics
> there that I fail to recall.
Sounds like nonblocking read/write calls are strongly tied to threads
instead of state related to a file descriptor. I haven't poked around
in there, but perhaps the current linux io architecture is just too
set in stone to design an efficient non blocking mechanism. It would
be a shame not to fix it simply because some broken apps depend upon
blocking behavior when they have been explicitly specifying O_NONBLOCK
via open or fcntl.
At least for now we can describe it's actual behavior in the man
pages; I will be submitting a man page patch for consideration later
today.
- Mike
next prev parent reply other threads:[~2010-03-05 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B904D98.50602@gmail.com>
2010-03-05 1:39 ` M vd S
2010-03-05 16:03 ` Jeff Moyer
2010-03-05 19:43 ` Mike Hayward [this message]
2010-03-10 0:50 ` M vd S
2010-03-10 13:21 ` Jeff Moyer
2010-03-10 17:09 ` M vd S
[not found] ` <201003102350.o2ANousd007794@alien.loup.net>
[not found] ` <4B983E88.5080901@gmail.com>
2010-03-11 7:41 ` Mike Hayward
2010-03-03 8:26 Mike Hayward
2010-03-03 11:50 ` Alan Cox
2010-03-03 19:49 ` Mike Hayward
2010-03-03 21:25 ` Alan Cox
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=201003051943.o25Jhs6w012994@alien.loup.net \
--to=hayward@loup.net \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mvds.00@gmail.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®