From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH] mballoc: allocate stripe-multiple IOs on stripe boundaries
Date: Mon, 26 Jul 2010 18:52:23 -0400 [thread overview]
Message-ID: <20100726225223.GB14072@thunk.org> (raw)
In-Reply-To: <4C3E27BF.2000005@redhat.com>
On Wed, Jul 14, 2010 at 04:10:23PM -0500, Eric Sandeen wrote:
> For some reason, today mballoc only allocates IOs which are exactly
> stripe-sized on a stripe boundary. If you have a multiple (say, a
> 128k IO on a 64k stripe) you may end up unaligned.
>
> It seems to me that a simple change to align stripe-multiple IOs
> on stripe boundaries would be a very good idea, unless this breaks
> some other mballoc heuristic for some reason...
I've added this to the ext4 tree, thanks.
- Ted
prev parent reply other threads:[~2010-07-26 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 21:10 [PATCH] mballoc: allocate stripe-multiple IOs on stripe boundaries Eric Sandeen
2010-07-14 21:33 ` Andreas Dilger
2010-07-26 22:52 ` Ted Ts'o [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=20100726225223.GB14072@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=snitzer@redhat.com \
/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