Message-ID: <5385EEF5.9050904@gmail.com>
Date: Wed, 28 May 2014 10:13:09 -0400
From: Anna Schumaker <schumaker.anna@gmail.com>
MIME-Version: 1.0
To: "J. Bruce Fields" <bfields@redhat.com>,
        Christoph Hellwig <hch@infradead.org>
CC: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 41/52] nfsd4: turn off zero-copy-read in exotic cases
References: <1400787148-25941-1-git-send-email-bfields@redhat.com> <1400787148-25941-42-git-send-email-bfields@redhat.com> <20140528080945.GA6797@infradead.org> <20140528140151.GB13012@pad.redhat.com>
In-Reply-To: <20140528140151.GB13012@pad.redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-nfs-owner@vger.kernel.org

On 05/28/2014 10:01 AM, J. Bruce Fields wrote:
> On Wed, May 28, 2014 at 01:09:45AM -0700, Christoph Hellwig wrote:
>> On Thu, May 22, 2014 at 03:32:16PM -0400, J. Bruce Fields wrote:
>>> Later patches handle those "exotic compounds", this one just makes sure
>>> zero-copy is turned off in those cases.
>> How did you test these exotic compounds?
> I have is a pynfs test that sends a compound with multiple reads in it.
>
> I don't think that's pushed out to my regular pynfs tree, I'll try to do
> that today.
>
> I could really use more of those.  Maybe I'm wrong, but I'm worried less
> about this case than the more finicky out-of-reply-space cases, where I
> do have patches puporting to fix problems that I haven't really
> verified.

I'll eventually be using this case for READ_PLUS.  I'll be sure to send problems your way! :)

Anna
>
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html