linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Chris Mason <chris.mason@oracle.com>,
	linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: ext4 writepages is making tiny bios?
Date: Tue, 1 Sep 2009 17:27:40 -0400	[thread overview]
Message-ID: <20090901212740.GA9930@infradead.org> (raw)
In-Reply-To: <20090901205744.GE6996@mit.edu>

On Tue, Sep 01, 2009 at 04:57:44PM -0400, Theodore Tso wrote:
> > This graph shows the difference:
> > 
> > http://oss.oracle.com/~mason/seekwatcher/trace-buffered.png
> 
> Wow, I'm surprised how seeky XFS was in these graphs compared to ext4
> and btrfs.  I wonder what was going on.

XFS did the mistake of trusting the VM, while everyone more or less
overrode it.  Removing all those checks and writing out much larger
data fixes it with a relatively small patch:

	http://verein.lst.de/~hch/xfs/xfs-writeback-scaling

when that code was last benchamrked extensively (on SLES9) it
worked nicely to saturate extremly large machines using buffered
I/O, since then VM tuning basically destroyed it.


  reply	other threads:[~2009-09-01 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 18:44 ext4 writepages is making tiny bios? Chris Mason
2009-09-01 20:57 ` Theodore Tso
2009-09-01 21:27   ` Christoph Hellwig [this message]
2009-09-02  0:17     ` Chris Mason
2009-09-03  5:52     ` Dave Chinner
2009-09-03 16:42       ` Christoph Hellwig
2009-09-04  0:15         ` Theodore Tso
2009-09-04  7:20           ` Jens Axboe

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=20090901212740.GA9930@infradead.org \
    --to=hch@infradead.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).