From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fieldses.org ([173.255.197.46]:49438 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751001AbeBACkF (ORCPT ); Wed, 31 Jan 2018 21:40:05 -0500 Date: Wed, 31 Jan 2018 21:40:05 -0500 To: ronnie sahlberg Cc: Chuck Lever , Matthew Wilcox , lsf-pc@lists.linux-foundation.org, linux-fsdevel Subject: Re: [LSF/MM TOPIC] Compounding support in CIFS.KO Message-ID: <20180201024005.GE3814@fieldses.org> References: <20180131220316.GE28275@bombadil.infradead.org> <5BE73CAA-F18B-4D2F-9BCB-FFCD3786E2C3@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: From: bfields@fieldses.org (J. Bruce Fields) Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Feb 01, 2018 at 08:22:03AM +1000, ronnie sahlberg wrote: > I think you are right. The topic of cifs compounding is only really > interesting to cifs folks and not many others. While other > filesystems such as NFSv4 has compounding too, the way compounding > works in cifs is different enough that there is little meaningful > overlap between the two. I'm trying to remember what people have found to be the obstacles to more aggressive use of compounds in NFS. (Things like opening a file and doing IO to it in one compound.) Might it be more practical with some VFS changes? Are there some shared CIFS/NFS issues there? Anyway, the hallway track is fine.... --b.