From: Boaz Harrosh <bharrosh@panasas.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Peng Tao <bergwolf@gmail.com>, Benny Halevy <bhalevy@tonian.com>,
"Adamson, Andy" <William.Adamson@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>,
"Isaman, Fred" <Fred.Isaman@netapp.com>,
"Welch, Brent" <welch@panasas.com>,
Garth Gibson <garth.gibson@panasas.com>
Subject: Re: [PATCH] NFSv4.1: Remove a bogus BUG_ON() in nfs4_layoutreturn_done
Date: Tue, 14 Aug 2012 03:28:26 +0300 [thread overview]
Message-ID: <50299BAA.40909@panasas.com> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA93A064E@SACEXCMBX04-PRD.hq.netapp.com>
On 08/14/2012 03:16 AM, Myklebust, Trond wrote:
>
> The client can't guarantee that. The protocol offers no way for it to do
> so, no matter what the pNFS text may choose to say.
>
What? why not? all the client needs to do is stop sending bytes.
What is not guarantied? I completely do not understand what you
say. How stopping any sends does not guaranty that?
Please explain
Thanks
Boaz
next prev parent reply other threads:[~2012-08-14 0:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 20:21 [PATCH] NFSv4.1: Remove a bogus BUG_ON() in nfs4_layoutreturn_done Trond Myklebust
2012-08-09 14:30 ` Peng Tao
2012-08-09 14:36 ` Myklebust, Trond
2012-08-09 15:01 ` Peng Tao
2012-08-09 15:39 ` Myklebust, Trond
2012-08-09 16:22 ` Peng Tao
2012-08-09 16:29 ` Myklebust, Trond
2012-08-09 16:40 ` Peng Tao
2012-08-09 17:06 ` Peng Tao
2012-08-12 17:36 ` Boaz Harrosh
2012-08-13 16:26 ` Myklebust, Trond
2012-08-13 23:39 ` Boaz Harrosh
2012-08-14 0:16 ` Myklebust, Trond
2012-08-14 0:28 ` Boaz Harrosh [this message]
2012-08-14 0:49 ` Myklebust, Trond
[not found] ` <1344875167.7706.31.camel@lade.trondhjem.org>
2012-08-13 16:58 ` Myklebust, Trond
2012-08-14 7:48 ` Benny Halevy
2012-08-14 13:45 ` Myklebust, Trond
2012-08-14 14:30 ` Peng Tao
2012-08-14 14:53 ` Myklebust, Trond
2012-08-15 11:50 ` Benny Halevy
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=50299BAA.40909@panasas.com \
--to=bharrosh@panasas.com \
--cc=Fred.Isaman@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=William.Adamson@netapp.com \
--cc=bergwolf@gmail.com \
--cc=bhalevy@tonian.com \
--cc=garth.gibson@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
--cc=welch@panasas.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).