linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Chris Mason <chris.mason@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-mm@kvack.org,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, jens
Subject: Re: [PATCH, RFC] vm: Add an tuning knob for vm.max_writeback_pages
Date: Tue, 1 Sep 2009 16:30:22 -0400	[thread overview]
Message-ID: <20090901203022.GD6996@mit.edu> (raw)
In-Reply-To: <20090901180052.GA7885@think>

On Tue, Sep 01, 2009 at 02:00:52PM -0400, Chris Mason wrote:
> 
> I haven't yet tried this without the max_writeback_pages patch, but the
> graphs clearly show a speed improvement, and that the mainline code is
> smearing writes across the drive while Jens' work is writing
> sequentially.

FYI, you don't need to revert the max_writebacks_pages patch; the
whole point of making it a tunable was to make it easier to run
benchmarks.  If you want to get the effects of the original setting of
MAX_WRITEBACK_PAGES before the patch, just run as root: 

    sysctl vm.max_writeback_pages=1024

						- Ted

      reply	other threads:[~2009-09-01 20:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1251600858-21294-1-git-send-email-tytso@mit.edu>
2009-08-30 16:52 ` [PATCH, RFC] vm: Add an tuning knob for vm.max_writeback_pages Christoph Hellwig
2009-08-30 18:17   ` Theodore Tso
2009-08-30 22:27     ` Christoph Hellwig
2009-08-31  3:08       ` Theodore Tso
2009-08-31 10:29         ` Jens Axboe
2009-08-31 10:47           ` Jens Axboe
2009-08-31 12:37             ` Theodore Tso
2009-08-31 15:54             ` Theodore Tso
2009-08-31 20:36               ` Jens Axboe
2009-08-31 21:03             ` Theodore Tso
2009-09-01  7:57               ` Aneesh Kumar K.V
2009-09-01  9:17               ` Jens Axboe
2009-09-01 18:00     ` Chris Mason
2009-09-01 20:30       ` Theodore Tso [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=20090901203022.GD6996@mit.edu \
    --to=tytso@mit.edu \
    --cc=chris.mason@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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).