From: Greg Banks <gnb@melbourne.sgi.com>
To: Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: O_NONBLOCK for regular files
Date: Wed, 13 Apr 2005 10:45:53 +1000 [thread overview]
Message-ID: <1113353153.1956.481.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <405C0DC0.3E61994@melbourne.sgi.com>
G'day,
On Sat, 2004-03-20 at 20:24, Greg Banks wrote:
> Jamie Lokier wrote:
> > Christoph Hellwig wrote:
> > > It's used to [...] return EAGAIN to the nfs server so it doesn't block all
> > > nfsd threads on possible long-enduring HSM operations.
> >
> > How does nfsd get notified when the operation is possible?
>
> It doesn't; the nfsd sends an RPC reply containing the NFSERR_JUKEBOX
> error to the NFS client, which sleeps and retries the operation after a
> few seconds. If the operation is not yet possible the cycle repeats.
http://marc.theaimsgroup.com/?l=linux-fsdevel&m=107959907311576&w=2
This thread was started by Christoph Hellwig 13 months ago to discuss
the possibility of using O_NONBLOCK in nfsd to make the combination
of NFS and Hierarchical Storage Managers play nicely together. The
thread petered out with no firm conclusion but no major objections
either.
There's now a patch to actually do it, see
http://marc.theaimsgroup.com/?l=linux-nfs&m=111087383132762&w=2
Does anyone want to give a firm yea or nea to this approach? I'd
really like to get this patch moving in the pipeline.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-04-13 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 9:24 O_NONBLOCK for regular files Greg Banks
2005-04-13 0:45 ` Greg Banks [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-03-18 8:36 Christoph Hellwig
2004-03-18 8:42 ` viro
2004-03-18 8:45 ` Christoph Hellwig
2004-03-18 10:48 ` Stephen Rothwell
2004-03-18 12:05 ` Jamie Lokier
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=1113353153.1956.481.camel@hole.melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).