From: "H. Peter Anvin" <hpa@zytor.com>
To: James Andrewartha <jamesa@daa.com.au>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Matthew Wilcox <matthew@wil.cx>, Theodore Tso <tytso@mit.edu>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
sandeen@redhat.com
Subject: Re: ATA support for 4k sector size
Date: Thu, 10 Dec 2009 23:26:39 -0800 [thread overview]
Message-ID: <4B21F42F.4070400@zytor.com> (raw)
In-Reply-To: <4B21EF54.9070609@daa.com.au>
On 12/10/2009 11:05 PM, James Andrewartha wrote:
> Martin K. Petersen wrote:
>>>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:
>>
>> Matthew> Lowest aligned logical block address=0
>>
>> Matthew> This disagrees with Martin's assertion.
>>
>> The original roadmap was to transition to 4KB sectors in 2006,
>> coinciding with the Vista release.
>>
>> Given how long this has taken (we're now talking ~2011 for GA) it may
>> very well be that the alignment knobs will be unused because everybody
>> will be using Vista or 7 by then.
>
> The plan does seem to have changed - WD's shipping 4k sector drives that
> are sane and require a drive jumper or tool for WinXP and old cloning
> utilities.
>
> http://techreport.com/discussions.x/18115
> http://wdc.com/en/products/advancedformat/
> http://www.wdc.com/wdproducts/library/whitepapers/en/2579-771430-A00.pdf
>
Even more important, the alignment can be changed as opposed to being
fixed for the manufacture of the disk.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-12-11 7:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 22:24 ATA support for 4k sector size Matthew Wilcox
2009-02-25 22:24 ` [PATCH 1/2] ata: Define new commands from ATA8 Matthew Wilcox
2009-02-25 22:24 ` [PATCH 2/2] ata: Add support for Long Logical Sectors and Long Physical Sectors Matthew Wilcox
2009-02-25 22:53 ` ATA support for 4k sector size H. Peter Anvin
2009-02-25 23:27 ` Martin K. Petersen
2009-02-25 23:33 ` H. Peter Anvin
2009-02-25 23:51 ` Martin K. Petersen
2009-02-26 12:43 ` Karel Zak
2009-02-26 15:17 ` H. Peter Anvin
2009-02-25 23:42 ` H. Peter Anvin
2009-02-25 23:55 ` Martin K. Petersen
2009-02-25 23:57 ` H. Peter Anvin
2009-02-26 0:07 ` Martin K. Petersen
2009-02-26 0:10 ` H. Peter Anvin
2009-02-26 0:17 ` Martin K. Petersen
2009-02-25 23:49 ` david
2009-02-26 0:04 ` Martin K. Petersen
2009-02-26 0:13 ` david
2009-02-26 0:20 ` Martin K. Petersen
2009-02-26 2:50 ` Theodore Tso
2009-02-26 3:05 ` Martin K. Petersen
2009-02-26 3:07 ` Matthew Wilcox
2009-02-26 3:23 ` Martin K. Petersen
2009-12-11 7:05 ` James Andrewartha
2009-12-11 7:26 ` H. Peter Anvin [this message]
2009-12-11 7:32 ` Martin K. Petersen
2009-02-26 5:16 ` Martin K. Petersen
2009-02-26 12:36 ` Matthew Wilcox
2009-02-26 15:32 ` H. Peter Anvin
2009-02-26 20:35 ` Martin K. Petersen
2009-02-26 21:02 ` H. Peter Anvin
2009-03-16 14:51 ` Greg Freemyer
2009-03-16 16:27 ` H. Peter Anvin
2009-03-16 17:37 ` Greg Freemyer
2009-03-16 18:11 ` H. Peter Anvin
2009-03-22 1:20 ` Bill Davidsen
2009-03-18 14:33 ` James Bottomley
2009-02-26 18:22 ` hdparm-9.12 released Mark Lord
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=4B21F42F.4070400@zytor.com \
--to=hpa@zytor.com \
--cc=jamesa@daa.com.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthew@wil.cx \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).