linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Sonny Rao <sonny@burdell.org>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-fsdevel@vger.kernel.org
Subject: Re: ext3 writepages ?
Date: 09 Feb 2005 14:29:04 -0800	[thread overview]
Message-ID: <1107988144.20053.79.camel@dyn318077bld.beaverton.ibm.com> (raw)
In-Reply-To: <20050209211123.GA10554@kevlar.burdell.org>

On Wed, 2005-02-09 at 13:11, Sonny Rao wrote:
> On Tue, Feb 08, 2005 at 12:38:08AM -0500, Sonny Rao wrote:
> > On Mon, Feb 07, 2005 at 06:33:51PM -0700, Andreas Dilger wrote:
> > > On Feb 03, 2005  15:50 -0500, Sonny Rao wrote:
> > > > Well, from what I can tell, my patch doesn't seem to make much of a
> > > > difference in write throughput other than allowing multi-page bios to
> > > > be sent down and cutting down on buffer_head usage.
> > > 
> > > Even if it doesn't make a difference in performance, it might reduce the
> > > CPU usage.  Did you check that at all?
> > 
> > No I didn't, I'll check that out and post back.
> > 
> > Sonny
> 
> Ok, I take it back, on a raid device I saw a significant increase in
> throughput and approximately equal cpu utilization.   I was comparing
> the wrong data points before.. oops.
> 
> Sequential overwrite went from 75.6 MB/sec to 87.7 MB/sec both with an
> average CPU utilization of 73% for both.
> 
> So, I see a 16% improvement in throughput for this test case and a
> corresponding increase in efficiency. 
> 
> Although, after reading what SCT wrote about writepage and writepages
> needing to have a transaction handle, in some cases, that might  make
> the proper writepages code significantly more complex than my two-bit
> hack.  Still, I think it's worth it.

Yep. I hacked ext3_write_pages() to use mpage_writepages() as you did
(without modifying bufferheads stuff). With the limited testing I did,
I see much larger IO chunks and better throughput. So, I guess its
worth doing it - i am little worried about error handling though..

Lets handle one issue at a time. 

First fix writepages() without bufferhead changes ? Then handle
bufferheads ? I still can't figure out a way to workaround the
bufferheads especially for ordered writes.

Thanks,
Badari


  reply	other threads:[~2005-02-09 22:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 15:32 ext3 writepages ? Badari Pulavarty
2005-02-02 20:19 ` Sonny Rao
2005-02-03 15:51   ` Badari Pulavarty
2005-02-03 17:00     ` Sonny Rao
2005-02-03 16:56       ` Badari Pulavarty
2005-02-03 17:24         ` Sonny Rao
2005-02-03 20:50     ` Sonny Rao
2005-02-08  1:33       ` Andreas Dilger
2005-02-08  5:38         ` Sonny Rao
2005-02-09 21:11           ` Sonny Rao
2005-02-09 22:29             ` Badari Pulavarty [this message]
2005-02-10  2:05               ` Bryan Henderson
2005-02-10  2:45                 ` Sonny Rao
2005-02-10 17:51                   ` Bryan Henderson
2005-02-10 19:02                     ` Sonny Rao
2005-02-10 16:02                 ` Badari Pulavarty
2005-02-10 18:00                   ` Bryan Henderson
2005-02-10 18:32                     ` Badari Pulavarty
2005-02-10 20:30                       ` Bryan Henderson
2005-02-10 20:25                         ` Sonny Rao
2005-02-11  0:20                           ` Bryan Henderson

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=1107988144.20053.79.camel@dyn318077bld.beaverton.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sonny@burdell.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).