linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Whitney <eric.whitney@hp.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 kernel patches ready for benchmarking
Date: Sun, 13 Mar 2011 23:04:27 -0400	[thread overview]
Message-ID: <4D7D85BB.20503@hp.com> (raw)
In-Reply-To: <E1PuaLr-0001dQ-Hr@tytso-glaptop>

On 03/01/2011 07:55 PM, Theodore Ts'o wrote:
> Hi Eric (and the rest of the ext4 development team),
>
> I still have some ext4 patches to merge, but all or most of the ones
> that should affect performance are in the ext4 tree now.  You can get
> them via
>
>     git fetch git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git \
> 		for-enw-benchmark
>
> This patch series is based off of 2.6.38-rc5, plus one fixup commit,
> 3abb17e82f: "vfs: fix BUG_ON() in fs/namei.c:1461", which shouldn't be
> performance relevant (FFSB doesn't use symlinks, which is probably why
> you haven't noticed any problems).
>
> This patch series has passed a large number of xfstests runs using 4k
> and 1k block sizes.  I am currently using this patch set merged with
> 2.6.38-rc7 on my laptop, and it "feels" faster, but could be becauses of
> other optimizations and improvements that went in post-2.6.38, and it
> could be because I've enabled CONFIG_SCHED_AUTOGROUP, not just the ext4
> improvements :-)  --- although commit b616844 could very well help
> synchronous write workloads.
>

<snip>

Hi Ted:

My test results for this patch series are now available for review at:
http://free.linux.hp.com/~enw/ext4/2.6.38-rc5

For this set of runs, I've also tried reworking my old system 
utilization graphs to better reflect per transaction efficiency ("CPU 
Cost").

Thanks for the patches!
Eric

      reply	other threads:[~2011-03-14  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02  0:55 Ext4 kernel patches ready for benchmarking Theodore Ts'o
2011-03-14  3:04 ` Eric Whitney [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=4D7D85BB.20503@hp.com \
    --to=eric.whitney@hp.com \
    --cc=linux-ext4@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).