From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from bombadil.infradead.org ([198.137.202.9]:42767 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754895Ab3J2NiB (ORCPT ); Tue, 29 Oct 2013 09:38:01 -0400 Date: Tue, 29 Oct 2013 06:38:00 -0700 From: Christoph Hellwig To: "J. Bruce Fields" Cc: Christoph Hellwig , Anna Schumaker , linux-nfs@vger.kernel.org Subject: Re: [RFC 5/4] NFSD: Add basic CB_OFFLOAD support Message-ID: <20131029133800.GA27762@infradead.org> References: <1382972247-1108-1-git-send-email-bjschuma@netapp.com> <1382972247-1108-6-git-send-email-bjschuma@netapp.com> <20131028215221.GQ31322@fieldses.org> <20131029073719.GB10889@infradead.org> <20131029133611.GF29606@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20131029133611.GF29606@fieldses.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Oct 29, 2013 at 09:36:11AM -0400, J. Bruce Fields wrote: > Yeah, understood, I'm glad we're not implementing that, I just wonder > why every one of these operations (COPY, WRITE_PLUS, etc.) has to have > this asynchronous option. > > The client's still stuck implementing it even if the server does, it's > extra protocol verbage even if nobody uses it, and I'm not completely > clear what it's for. Seems like Trond answered that question: feature creep that people without the slightest sense of abstraction tried to overload over a few operations.