public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd.bergmann@linaro.org>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: Saugata Das <saugata.das@linaro.org>,
	Saugata Das <saugata.das@stericsson.com>,
	linux-mmc@vger.kernel.org, venkat@linaro.org, patches@linaro.org,
	lporzio@micron.com
Subject: Re: [PATCH 1/2] [MMC-4.5] Disable emulation
Date: Thu, 17 May 2012 07:07:34 +0000	[thread overview]
Message-ID: <201205170707.34674.arnd.bergmann@linaro.org> (raw)
In-Reply-To: <CAKYAXd_pNg0MwX5vR2Pegn0UeSX3=qO4WU70QExfiFooD8yLuw@mail.gmail.com>

On Thursday 17 May 2012, Namjae Jeon wrote:
> 2012/5/17, Saugata Das <saugata.das@linaro.org>:
> > On 17 May 2012 06:35, Namjae Jeon <linkinjeon@gmail.com> wrote:
> >> 2012/5/17, Saugata Das <saugata.das@stericsson.com>:
> >> If you change native 4K from 512B emulation, filesystem sector size is
> >> also 4KB align as well block size.
> >> because default block size of most of filesystem is 4KB, but
> >> filesystem sector size is 512B,
> >> So filesystem corruption can be occured on native 4K device.
> >>>
> >
> > I have tested ext4 with 4KB block size and I did not see an instance
> > where it requested 512B.
> -> yes, you can not see it, because when formating parittion, sector
> size is set to 4K by I/O topology. As you know, several filesystems
> can be used on eMMC not only Ext4. You should mention filesystem
> sector size align in changelog.

It's important to note here that if someone tries to use a block size
of less than 4KB on eMMC, or has a misaligned partition, that is already
a mistake and causes increased wear and reduced performance. Forcing 4KB
alignment is defintely a good idea and I would recommend setting the
'disable emulation' flag on all hardware that allows it just for this
reason.

Also note that hard drives and SSDs are also moving to 4KB hard sector
size and other block devices (DVD-RAM, DASD, ...) have only supported
larger sectors since the start and can be used with most file systems.

	Arnd

      parent reply	other threads:[~2012-05-17  7:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 16:26 [PATCH 1/2] [MMC-4.5] Disable emulation Saugata Das
2012-05-16 16:26 ` [PATCH 2/2] [MMC-4.5] [MMC UTIL] " Saugata Das
2012-05-17  7:48   ` Subhash Jadavani
2012-05-17 11:07     ` Saugata Das
2012-05-17  1:05 ` [PATCH 1/2] [MMC-4.5] " Namjae Jeon
2012-05-17  3:12   ` Saugata Das
2012-05-17  3:34     ` Namjae Jeon
2012-05-17  4:47       ` Saugata Das
2012-05-17  5:05         ` Saugata Das
2012-05-17  7:07       ` Arnd Bergmann [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=201205170707.34674.arnd.bergmann@linaro.org \
    --to=arnd.bergmann@linaro.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lporzio@micron.com \
    --cc=patches@linaro.org \
    --cc=saugata.das@linaro.org \
    --cc=saugata.das@stericsson.com \
    --cc=venkat@linaro.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