mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.11-mm1 ext3 writepages support for writeback mode
Date: 04 Mar 2005 15:58:05 -0800	[thread overview]
Message-ID: <1109980684.7236.35.camel@dyn318077bld.beaverton.ibm.com> (raw)
In-Reply-To: <20050304154346.488b0a14.akpm@osdl.org>

On Fri, 2005-03-04 at 15:43, Andrew Morton wrote:
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > Hi Andrew,
> > 
> > Here is the 2.6.11-mm1 patch for adding writepages support
> > for ext3 writeback mode. Could you include it in -mm tree ?
> 
> spose so.  Does it work?
> 
> Do you have any benchmarking results handy?

I did few benchmarks earlier which showed 5-7% improvement
on throughput. I will run the numbers again.

> 
> > +static int
> > +ext3_writeback_writepages(struct address_space *mapping, 
> > +				struct writeback_control *wbc)
> > +{
> > +	struct inode *inode = mapping->host;
> > +	handle_t *handle = NULL;
> > +	int err, ret = 0;
> > +
> > +	if (!mapping_tagged(mapping, PAGECACHE_TAG_DIRTY))
> > +		return ret;
> 
> Can we please add a comment explaining why this is here?  I've already
> forgotten why we put it there.

This is to avoid not starting the journal when we are trying to
destroy journal inode. I will add comments.

>       journal_destory()
>               iput(journal inode)
>                       do_writepages()
>                               generic_writepages()
>                                       ext3_writeback_writepage()
>                                               journal_start()

 
Thanks,
Badari



      reply	other threads:[~2005-03-05  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 23:21 Badari Pulavarty
2005-03-04 23:43 ` Andrew Morton
2005-03-04 23:58   ` Badari Pulavarty [this message]

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=1109980684.7236.35.camel@dyn318077bld.beaverton.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.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

all inboxes | Powered by JetHome®