From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>
Cc: "ZUIDAM, Hans" <Hans.Zuidam@philips.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"DE WITTE, PETER" <PETER.DE.WITTE@philips.com>
Subject: Re: Linux NFS and cached properties
Date: Tue, 31 Jul 2012 10:07:54 -0400 [thread overview]
Message-ID: <20120731140754.GA27834@fieldses.org> (raw)
In-Reply-To: <20120731124550.GA27135@fieldses.org>
On Tue, Jul 31, 2012 at 08:45:50AM -0400, J. Bruce Fields wrote:
> On Tue, Jul 31, 2012 at 08:25:46AM -0400, J. Bruce Fields wrote:
> > On Tue, Jul 31, 2012 at 03:08:01PM +1000, NeilBrown wrote:
> > > The idea of a new interface to synchronise with all threads has potential and
> > > doesn't need to be at the nfsd level - it could be in sunrpc. Maybe it could
> > > be built into the current 'flush' interface.
>
> The flush operation will have to know which services to wait on when
> flushing a given cache (lockd and nfsd in the export cache cases).
>
> A little annoying that it may end up having to wait on a client-side
> operation in the case of lockd, but I don't think that's a show-stopper.
Ignore me, I wasn't thinking straight: a lockd thread won't of course be
waiting on client rpc's to a server, it will just be handling callbacks,
which should be very quick.
--b.
next prev parent reply other threads:[~2012-07-31 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D307B3AC0BCD4C419E6B8FA6A2720A9C0C3B2F@011-DB3MPN1-001.MGDPHG.emi.philips.com>
[not found] ` <20120724143748.GC8570@fieldses.org>
2012-07-24 17:28 ` Linux NFS and cached properties ZUIDAM, Hans
2012-07-26 22:36 ` J. Bruce Fields
2012-07-31 5:08 ` NeilBrown
2012-07-31 12:25 ` J. Bruce Fields
2012-07-31 12:45 ` J. Bruce Fields
2012-07-31 14:07 ` J. Bruce Fields [this message]
2012-08-02 0:04 ` NeilBrown
2012-08-02 2:50 ` J. Bruce Fields
2012-08-16 19:10 ` J. Bruce Fields
2012-08-16 21:05 ` NeilBrown
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=20120731140754.GA27834@fieldses.org \
--to=bfields@fieldses.org \
--cc=Hans.Zuidam@philips.com \
--cc=PETER.DE.WITTE@philips.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).