From: Arnd Bergmann <arnd@arndb.de>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Andrei Warkentin <andreiw@motorola.com>,
linux-mmc@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [RFC 4/5] MMC: Adjust unaligned write accesses.
Date: Mon, 21 Mar 2011 20:05:37 +0100 [thread overview]
Message-ID: <201103212005.37108.arnd@arndb.de> (raw)
In-Reply-To: <C0A67981-AF1A-40FF-91BA-93ECF6F72B58@dilger.ca>
On Monday 21 March 2011 19:03:09 Andreas Dilger wrote:
> Note that mballoc was specifically designed to handle allocation
> requests that are aligned on RAID stripe boundaries, so it should
> be able to handle this for MMC as well. What is needed is to tell
> the filesystem what the underlying alignment is. That can be done
> at format time with mke2fs or afterward with tune2fs by using the
> "-E stripe_width" option.
Ah, that sounds useful. So would I set the stripe_width to the
erase block size, and the block group size to a multiple of that?
Does this also work in (rare) cases where the erase block size is
not a power of two?
Arnd
next prev parent reply other threads:[~2011-03-21 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1299718449-15172-1-git-send-email-andreiw@motorola.com>
[not found] ` <AANLkTimV-no9Wk4wbS4gQGdSgq-2L=ims6SXDFrdEZAe@mail.gmail.com>
[not found] ` <AANLkTinEQEwa2SqEwTnbe3kcYuDoM-ZbzWE7X+V3B+zV@mail.gmail.com>
2011-03-21 14:21 ` [RFC 4/5] MMC: Adjust unaligned write accesses Arnd Bergmann
2011-03-21 14:41 ` Andrei Warkentin
2011-03-21 18:03 ` Andreas Dilger
2011-03-21 19:05 ` Arnd Bergmann [this message]
2011-03-21 23:58 ` Andreas Dilger
2011-03-22 13:56 ` Arnd Bergmann
2011-03-22 15:02 ` Andreas Dilger
2011-03-22 15:44 ` Arnd Bergmann
2011-03-21 14:27 Fwd: " Arnd Bergmann
2011-03-21 23:45 ` Andreas Dilger
2011-03-22 7:18 ` Andrei Warkentin
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=201103212005.37108.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=adilger@dilger.ca \
--cc=andreiw@motorola.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mmc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox