From: Jim Rees <rees@umich.edu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Benny Halevy <bhalevy@tonian.com>, Peng Tao <bergwolf@gmail.com>,
linux-nfs@vger.kernel.org, Peng Tao <peng_tao@emc.com>,
nfsv4 list <nfsv4@ietf.org>
Subject: Re: [PATCH 2/2] nfs41: handle BLK_LAYOUT CB_RECALL_ANY
Date: Mon, 31 Oct 2011 14:31:31 -0400 [thread overview]
Message-ID: <20111031183131.GA1925@umich.edu> (raw)
In-Reply-To: <1320085212.4714.48.camel@lade.trondhjem.org>
Trond Myklebust wrote:
I don't necessarily disagree with what you are saying, but I have yet to
see a single server side implementation of CB_RECALL_ANY, let alone any
numbers that indicate performance or responsiveness problems resulting
from our existing client-side implementation.
I therefore find it hard to understand why optimising this particular
code is such a high priority, or why a patch that is adding per-file
layoutreturns to initiate_bulk_draining() is going to help anything at
all.
Testing between the linux block layout client and the EMC block layout
server revealed a deadlock when the server had handed out some number of
layouts and couldn't hand out any more. So now the EMC block layout server
implements CB_RECALL_ANY. So yes, this solves a real world problem, and
yes, there is a server that implements this.
We had some discussions at the time, and I don't remember if those were on
the linux-nfs list or in some other forum. We decided that the client was
in the best position to decide which layouts were no longer needed, so we
needed some way for the server to tell the client to return some layouts
without specifying which ones. CB_RECALL_ANY seemed custom-made for this
purpose, so we used it.
I don't think it would be appropriate for the server to recall all layouts
when it only needs some of them back.
next prev parent reply other threads:[~2011-10-31 18:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:15 [PATCH 1/2 RESEND] NFS4: fix cb_recallany decode error Peng Tao
2011-10-31 15:15 ` [PATCH 2/2] nfs41: handle BLK_LAYOUT CB_RECALL_ANY Peng Tao
2011-10-31 15:49 ` Trond Myklebust
2011-10-31 16:38 ` Peng Tao
2011-10-31 16:45 ` Trond Myklebust
2011-10-31 17:02 ` Peng Tao
2011-10-31 17:08 ` Benny Halevy
2011-10-31 17:42 ` Trond Myklebust
2011-10-31 17:57 ` Benny Halevy
2011-10-31 18:20 ` Trond Myklebust
2011-10-31 18:23 ` [nfsv4] " Matt W. Benjamin
2011-10-31 18:31 ` Trond Myklebust
2011-10-31 18:31 ` Jim Rees [this message]
2011-10-31 18:39 ` Trond Myklebust
2011-11-01 5:29 ` tao.peng
2011-11-04 1:33 ` tao.peng
2011-10-31 21:42 ` [nfsv4] " Welch, Brent
2011-11-01 14:59 ` david.noveck
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=20111031183131.GA1925@umich.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.org \
--cc=peng_tao@emc.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;
as well as URLs for NNTP newsgroup(s).