All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: EXT4 is ~2X as slow as XFS (593MB/s vs 304MB/s) for writes?
Date: Fri, 26 Feb 2010 19:12:00 -0600	[thread overview]
Message-ID: <4B887160.2090606@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1002262006000.8247@p34.internal.lan>

Justin Piszcz wrote:
...

>> Were the filesystems created to align with raid geometry?
> Only default options were used except the mount options.  If that is the
> culprit, I have some more testing to do, thanks, will look into it.
> 
>>
>> mkfs.xfs has done that forever; mkfs.ext4 only will do so (automatically)
>> with recent kernel+e2fsprogs.
> How recent?

You're recent enough.  :)

mkfs.ext4 output should include the stripe info if it was found.

        printf(_("Block size=%u (log=%u)\n"), fs->blocksize,
                s->s_log_block_size);
        printf(_("Fragment size=%u (log=%u)\n"), fs->fragsize,
                s->s_log_frag_size);
        printf(_("Stride=%u blocks, Stripe width=%u blocks\n"),
               s->s_raid_stride, s->s_raid_stripe_width);
        printf(_("%u inodes, %llu blocks\n"), s->s_inodes_count,
               ext2fs_blocks_count(s));

etc.

-Eric

  reply	other threads:[~2010-02-27  1:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  0:31 EXT4 is ~2X as slow as XFS (593MB/s vs 304MB/s) for writes? Justin Piszcz
2010-02-27  0:46 ` Dmitry Monakhov
2010-02-27  1:05   ` Justin Piszcz
2010-02-27  1:05     ` Justin Piszcz
2010-02-28  0:56     ` Asdo
2010-02-28  9:59       ` Justin Piszcz
2010-02-27  0:51 ` Eric Sandeen
2010-02-27  1:08   ` Justin Piszcz
2010-02-27  1:12     ` Eric Sandeen [this message]
2010-02-27  1:28       ` Eric Sandeen
2010-02-27 10:14         ` Justin Piszcz
2010-02-27 10:51           ` Justin Piszcz
2010-02-27 11:09             ` Justin Piszcz
2010-02-27 11:36               ` Justin Piszcz
2010-02-28  5:42                 ` tytso
2010-02-28 14:55                   ` Justin Piszcz
2010-03-01  8:39                     ` Andreas Dilger
2010-03-01  9:21                       ` Justin Piszcz
2010-03-01 14:48                         ` Michael Tokarev
2010-03-01 15:07                           ` Justin Piszcz
2010-03-01 16:15                     ` Eric Sandeen
2010-02-28 23:50                 ` Dave Chinner
2010-03-02  0:08 ` Eric Sandeen
2010-03-02  0:37   ` Eric Sandeen

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=4B887160.2090606@redhat.com \
    --to=sandeen@redhat.com \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.