From: Christoph Hellwig <hch@infradead.org>
To: linux-fsdevel@vger.kernel.org
Subject: O_NONBLOCK for regular files
Date: Thu, 18 Mar 2004 08:36:28 +0000 [thread overview]
Message-ID: <20040318083628.A25565@infradead.org> (raw)
Guy,
any opinion on whether we should allow O_NONBLOCK for regular files?
XFS currently has this in as a leftover from IRIX, it's used to to allow
the HSM support code in XFS (not in the kernel.org code due to the horrible
design, just in the oss.sgi.com tree) to return EAGAIN to the nfs server
so it doesn't block all nfsd threads on possible long-enduring HSM operations.
People want to bring that thing over to Linux now which brought that
O_NONBLOCK thing on my radar. I don't see any direct problems with this
thing, but I don't want it as an undocumented XFS extension.
next reply other threads:[~2004-03-18 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 8:36 Christoph Hellwig [this message]
2004-03-18 8:42 ` O_NONBLOCK for regular files viro
2004-03-18 8:45 ` Christoph Hellwig
2004-03-18 10:48 ` Stephen Rothwell
2004-03-18 12:05 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2004-03-20 9:24 Greg Banks
2005-04-13 0:45 ` Greg Banks
2005-04-13 5:56 ` Trond Myklebust
2005-04-13 6:03 ` Greg Banks
2005-04-13 6:31 ` Trond Myklebust
2005-04-13 7:06 ` Greg Banks
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=20040318083628.A25565@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@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.