From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Fix O_SYNC speedup for generic_file_write_nolock
Date: Mon, 8 Nov 2004 18:02:23 +0530 [thread overview]
Message-ID: <20041108123223.GA4028@in.ibm.com> (raw)
In-Reply-To: <1099915544.3577.9.camel@laptop.fenrus.org>
On Mon, Nov 08, 2004 at 01:05:44PM +0100, Arjan van de Ven wrote:
> On Mon, 2004-11-08 at 17:23 +0530, Suparna Bhattacharya wrote:
> > 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 ?
>
> not really; none do so far so how about not adding the export until
> someone does use it ?
It is just like sync_page_range() from akpm's original O_SYNC speedup
patch. Andrew, do we keep or remove the export ?
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2004-11-08 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 10:07 [PATCH] Fix O_SYNC speedup for generic_file_write_nolock Suparna Bhattacharya
2004-11-08 10:04 ` Arjan van de Ven
2004-11-08 11:53 ` Suparna Bhattacharya
2004-11-08 12:05 ` Arjan van de Ven
2004-11-08 12:32 ` Suparna Bhattacharya [this message]
2004-11-08 15:20 ` Joel Becker
2004-11-08 15:31 ` Arjan van de Ven
2004-11-08 18:29 ` Joel Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041108123223.GA4028@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).