Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:51538 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751865AbeDQOET (ORCPT ); Tue, 17 Apr 2018 10:04:19 -0400 Date: Tue, 17 Apr 2018 10:04:18 -0400 From: "J. Bruce Fields" To: Olga Kornievskaia Cc: Olga Kornievskaia , Christoph Hellwig , linux-nfs Subject: Re: [PATCH v8 0/9] NFSD support for async COPY Message-ID: <20180417140417.GE10291@parsley.fieldses.org> References: <20180413170158.17589-1-kolga@netapp.com> <20180414072202.GA6514@infradead.org> <20180416214522.GC2634@parsley.fieldses.org> <20180417065203.GA15145@infradead.org> <20180417134141.GB10291@parsley.fieldses.org> <20180417135708.GD10291@parsley.fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180417135708.GD10291@parsley.fieldses.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Apr 17, 2018 at 09:57:08AM -0400, J. Bruce Fields wrote: > On Tue, Apr 17, 2018 at 09:43:45AM -0400, Olga Kornievskaia wrote: > > > On Apr 17, 2018, at 9:41 AM, J. Bruce Fields wrote: > > > Christoph said: "I'd like to see numbers for actual, real use cases." > > > Yes, I'd love to see that too. > > > > > > Is it possible to get testing on real hardware that we'd expect people > > > to use, with sufficient details about the setup that someone else could > > > reproduce the results? > > > > The numbers we presented was on real hardware. If you have any more questions regarding the setup please ask. > > Argh, sorry, you had to remind me once already: > > https://www.ietf.org/mail-archive/web/nfsv4/current/msg15379.html And there was a digression on the commit behavior, but important point to me was that it looked like the server-server copy was something close to what the hardware could do. (Well, 800-900Mb/s on gigabit, I assume that's not bad.) --b.