From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suparna Bhattacharya Subject: Re: [PATCH] Fix O_SYNC speedup for generic_file_write_nolock Date: Mon, 8 Nov 2004 17:23:53 +0530 Message-ID: <20041108115353.GA4068@in.ibm.com> References: <20041108100738.GA4003@in.ibm.com> <1099908278.3577.2.camel@laptop.fenrus.org> Reply-To: suparna@in.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: Received: from e4.ny.us.ibm.com ([32.97.182.104]:7139 "EHLO e4.ny.us.ibm.com") by vger.kernel.org with ESMTP id S261562AbUKHLoT (ORCPT ); Mon, 8 Nov 2004 06:44:19 -0500 To: Arjan van de Ven Content-Disposition: inline In-Reply-To: <1099908278.3577.2.camel@laptop.fenrus.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Nov 08, 2004 at 11:04:38AM +0100, Arjan van de Ven wrote: > > +EXPORT_SYMBOL(sync_page_range_nolock); > > > why adding this export? nothing appears to be using it (AIO isn't a module after all) > This doesn't have anything to do with AIO. Filesystems which implement the equivalent of generic_file_write_nolock may use sync_page_range_nolock for O_SYNC. Does that help clarify ? Regards Suparna -- Suparna Bhattacharya (suparna@in.ibm.com) Linux Technology Center IBM Software Lab, India