linux-kernel - Re: [ANNOUNCE] util-linux-ng v2.17 (stable)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100111201734.GA11674@elf.ucw.cz>
Date:	Mon, 11 Jan 2010 21:17:34 +0100
From:	Pavel Machek <pavel@....cz>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Karel Zak <kzak@...hat.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, util-linux-ng@...r.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.17 (stable)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/