mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Karel Zak <kzak@redhat.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	util-linux-ng@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.17 (stable)
Date: Mon, 11 Jan 2010 21:17:34 +0100	[thread overview]
Message-ID: <20100111201734.GA11674@elf.ucw.cz> (raw)
In-Reply-To: <4B4B5768.2040005@zytor.com>

On Mon 2010-01-11 08:52:56, H. Peter Anvin wrote:
> On 01/11/2010 06:05 AM, Pavel Machek wrote:
> >On Fri 2010-01-08 13:43:47, H. Peter Anvin wrote:
> >>On 01/08/2010 01:33 AM, Karel Zak wrote:
> >>>
> >>>fdisk:
> >>>    - the fdisk command aligns newly created partitions to minimum_io_size
> >>>      boundary ("minimum_io_size" is physical sector size or stripe chunk
> >>>      size on RAIDs).
> >>>
> >>>    - the fdisk command supports disks with alignment_offset now.
> >>>
> >>
> >>I think we should align, by default, much more aggressively than that --
> >>because frequently we just don't know what the real physical alignment
> >>is (think of flash media, which uses large erase blocks underneath.)
> >
> >Flash has special mapping layer, and does not care (SD/MMC), or is a
> >raw nand and can't be used as block device (smartmedia).
> >
> 
> Uhm, that's just plain wrong.
> 
> It doesn't matter if there is a "special mapping layer" -- if you're
> crossing multiple erase blocks you're still having more churn in
> your flash translation layer, with more wear on the device, and
> lower performance than if you didn't.

Eraseblocks really should not matter. It is not as if each logical
sector belongs to one eraseblock....

(OTOH, maybe the eraseblock *groups* that are basis for wear-leveling
do, or maybe firmware is doing something really really strange.)
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-01-11 20:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  9:33 Karel Zak
2010-01-08 21:43 ` H. Peter Anvin
2010-01-08 22:40   ` Andreas Dilger
2010-01-08 23:33     ` H. Peter Anvin
2010-01-11  6:36     ` Martin K. Petersen
2010-01-11  7:27       ` H. Peter Anvin
2010-01-11 14:05   ` Pavel Machek
2010-01-11 16:52     ` H. Peter Anvin
2010-01-11 20:17       ` Pavel Machek [this message]
2010-01-11 23:26         ` H. Peter Anvin
2010-01-12 13:33           ` Artem Bityutskiy
2010-01-12 13:35             ` Artem Bityutskiy
2010-01-11 19:17     ` Artem Bityutskiy
2010-01-12  7:19     ` Jörn Engel
2010-01-12  8:19       ` H. Peter Anvin
2010-01-12  9:37         ` Jörn Engel
2010-01-12 16:20           ` H. Peter Anvin

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=20100111201734.GA11674@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hpa@zytor.com \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux-ng@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

all inboxes | Powered by JetHome®