From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org, nfsv4 list <nfsv4@ietf.org>,
Benny Halevy <bhalevy@tonian.com>
Subject: Re: [nfsv4] [PATCH 2/2] nfs41: handle BLK_LAYOUT CB_RECALL_ANY
Date: Mon, 31 Oct 2011 14:23:10 -0400 (EDT) [thread overview]
Message-ID: <553963112.119.1320085390187.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1320085212.4714.48.camel@lade.trondhjem.org>
Hi,
Such a server implementation will certainly not be long in coming.
Matt
----- "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote:
> On Mon, 2011-10-31 at 19:57 +0200, Benny Halevy wrote:
> >
> > Waiting for revocation may work well with some servers but would be
> disastrous in
> > terms of performance and responsiveness with others.
>
> 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.
>
> Trond
>
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2011-10-31 18:24 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 ` Matt W. Benjamin [this message]
2011-10-31 18:31 ` [nfsv4] " Trond Myklebust
2011-10-31 18:31 ` Jim Rees
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=553963112.119.1320085390187.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.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.