From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Peter Grandi <pg@lxra2.for.sabi.co.UK>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Why 4k native drives haven't arrived
Date: Mon, 06 Jan 2014 18:50:24 -0500 [thread overview]
Message-ID: <yq161pwy8jj.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <21193.43286.201949.339364@tree.ty.sabi.co.uk> (Peter Grandi's message of "Sun, 5 Jan 2014 18:48:54 +0000")
>>>>> "Peter" == Peter Grandi <pg@lxra2.for.sabi.co.UK> writes:
Peter> There are some obvious wins to addressing in 4KiB sectors, the
Peter> most important of which is the avoidance of RMW as a possibility.
There are also drives where you can disable RMW explicitly. I.e. the
drive appears as 512e but will reject any misaligned non-multiple of 4K.
The downside to 4Kn is that it breaks applications using direct I/O that
assume that the sector size is 512 bytes. Which essentially means all of
them. Solaris opted to do RMW in software to overcome that issue.
Whereas we are trying to get application writers to fix their code...
Peter> But there is another important short term win, as older storage
Peter> protols and formats relate maximum disk or partition or filetree
Peter> capacity to maximum number of sectors addressable, which is often
Peter> fixed at below 2^32 or 2^31, so addresses in units of 4KiB
Peter> sectors allow 8 times more capacity than 512B ones.
Yep. Although in Linux we use 512-byte sectors throughout the I/O stack
regardless of the device's logical block size.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-01-06 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 1:53 Why 4k native drives haven't arrived Stan Hoeppner
2014-01-03 11:23 ` Mikael Abrahamsson
2014-01-03 11:27 ` Dimitri John Ledkov
2014-01-23 2:19 ` Phillip Susi
2014-01-03 21:04 ` Martin K. Petersen
2014-01-04 18:40 ` Stan Hoeppner
2014-01-06 23:35 ` Martin K. Petersen
2014-01-05 18:48 ` Peter Grandi
2014-01-06 23:50 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-09 21:49 Chris Murphy
2014-01-12 4:01 ` Chris Murphy
2014-01-12 13:55 ` Martin K. Petersen
[not found] ` <F92ECEC1-D375-498B-8C6A-C88C815C325F@colorremedies.com>
2014-01-12 18:32 ` Martin K. Petersen
2014-01-12 19:04 ` Chris Murphy
2014-01-12 19:27 ` Chris Murphy
2014-01-12 20:25 ` Roman Mamedov
2014-01-12 18:41 ` Stan Hoeppner
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=yq161pwy8jj.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=linux-raid@vger.kernel.org \
--cc=pg@lxra2.for.sabi.co.UK \
/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;
as well as URLs for NNTP newsgroup(s).