From: Al Viro Subject: Re: v9fs writepage Date: Sat, 30 Apr 2005 20:01:35 +0100 Message-ID: <20050430190135.GF13052@parcelfarce.linux.theplanet.co.uk> References: <20050430183653.GE13052@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Miklos Szeredi , v9fs-developer@lists.sourceforge.net, kernel-mentors@selenic.com, linux-fsdevel@vger.kernel.org, hch@infradead.org Return-path: Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:5319 "EHLO parcelfarce.linux.theplanet.co.uk") by vger.kernel.org with ESMTP id S261341AbVD3TBR (ORCPT ); Sat, 30 Apr 2005 15:01:17 -0400 To: Eric Van Hensbergen Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Apr 30, 2005 at 01:47:35PM -0500, Eric Van Hensbergen wrote: > Yes. I agree. I actually explicitly took all the cacheing behavior > out of v9fs when I started getting involved a year ago. I only put > the address_space operations back in recently in order to support mmap > (which isn't supported at all under Plan 9). Would you rather I > remove the vfs_addr.c support in order to stay more Plan 9 consistent? > I figured I'd have a better chance of getting LKML acceptance by > providing as many "linux semantics" as I could -- specifically we > really wanted to pass fsx. Well, let me put it that way: a) more complexity does not help to get new code merged. b) 9P has very obvious RPC-style uses. We have nothing really suitable in that area and implementation on non-caching 9P client has immediate applications. And _that_ is far more interesting than ability to import from Plan 9 fileserver or u9fs running on a Unix box. c) mmap() is and ever had been optional. If userland code breaks due to mmap() not working for some file - it's already fs-dependent.