From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [ANNOUNCE] new new aops patchset Date: Thu, 5 Apr 2007 08:45:29 +0100 Message-ID: <20070405074529.GB25196@infradead.org> References: <20070402120934.GA19626@wotan.suse.de> <20070405001018.GK32602149@melbourne.sgi.com> <20070405021305.GD11192@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Chinner , Linux Filesystems , Mark Fasheh , Steven Whitehouse To: Nick Piggin Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:59321 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946053AbXDEHpe (ORCPT ); Thu, 5 Apr 2007 03:45:34 -0400 Content-Disposition: inline In-Reply-To: <20070405021305.GD11192@wotan.suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Apr 05, 2007 at 04:13:05AM +0200, Nick Piggin wrote: > > On a related note - what's the rules for a perform_write() implementation? > > I noticed that wasn't documented with write_begin and write_end and > > I don't see any other filesystem implementing it yet.... > > Ah, so it isn't, thanks I'll document it. (today I'm looking at doing a > simple_perform_write and perhaps another easy one, which should also help > filesystem maintainers to have a reference). I think ->perform_write should go away. It's really just duplicating ->write for the !O_DIRECT case. Instead we should factor the remaining bits of generic_file_aio_write into nice helpers so that people that don't want to use the generic part can build their own ->write from these pieces.