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]
Date:	Wed, 22 Jan 2014 07:54:37 -0800
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Ric Wheeler <rwheeler@...hat.com>
Cc:	linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org,
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
	lsf-pc@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going
 beyond 4096 bytes

On Tue, 2014-01-21 at 22:04 -0500, Ric Wheeler wrote:
> One topic that has been lurking forever at the edges is the current 4k 
> limitation for file system block sizes. Some devices in production today and 
> others coming soon have larger sectors and it would be interesting to see if it 
> is time to poke at this topic again.
> 
> LSF/MM seems to be pretty much the only event of the year that most of the key 
> people will be present, so should be a great topic for a joint session.

But the question is what will the impact be.  A huge amount of fuss was
made about 512->4k.  Linux was totally ready because we had variable
block sizes and our page size is 4k.  I even have one pure 4k sector
drive that works in one of my test systems.

However, the result was the market chose to go the physical/logical
route because of other Operating System considerations, all 4k drives
expose 512 byte sectors and do RMW internally.  For us it becomes about
layout and alignment, which we already do.  I can't see how going to 8k
or 16k would be any different from what we've already done.  In other
words, this is an already solved problem.

James


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ