linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ATA support for 4k sector size
Date: Wed, 25 Feb 2009 14:53:43 -0800	[thread overview]
Message-ID: <49A5CBF7.9000501@zytor.com> (raw)
In-Reply-To: <1235600698-6446-1-git-send-email-matthew@wil.cx>

Matthew Wilcox wrote:
> The two patches following this add support for drives which have sector
> sizes other than 512 bytes.  I haven't been able to test this as I don't
> have the hardware.
> 
> Individual host drivers will have to be updated to support sizes other
> than 512 bytes.
> 
> Support for logical sector sizes that differ from physical sector sizes
> depends on the READ CAPACITY 16 patch I posted in December that isn't in
> scsi-misc yet.
> 
> The approach I've taken to generating the tables of which commands need
> a 512-byte transfer size and which use the drive's sector size command is
> 'innovative'.  Review is encouraged ;-)

What sector size do we report to user space for this?  I'm asking 
because logical sector size is visible in most partition formats.

	-hpa

  parent reply	other threads:[~2009-02-25 22:53 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 ` H. Peter Anvin [this message]
2009-02-25 23:27   ` ATA support for 4k sector size 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
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=49A5CBF7.9000501@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).