Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758082AbYG3Roc (ORCPT ); Wed, 30 Jul 2008 13:44:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752486AbYG3RoV (ORCPT ); Wed, 30 Jul 2008 13:44:21 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:39791 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752345AbYG3RoU (ORCPT ); Wed, 30 Jul 2008 13:44:20 -0400 Date: Wed, 30 Jul 2008 18:24:54 +0100 From: Alan Cox To: Matt Domsch Cc: Jim Meyering , "Martin K. Petersen" , James Bottomley , Matthew Wilcox , Ric Wheeler , linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, Jeff Garzik Subject: Re: tools support for non-512 byte sector sizes Message-ID: <20080730182454.25809628@lxorguk.ukuu.org.uk> In-Reply-To: <20080730172922.GA20191@auslistsprd01.us.dell.com> References: <488F524F.6020905@redhat.com> <20080729182611.GB24924@parisc-linux.org> <1217356645.6103.48.camel@localhost.localdomain> <20080730135147.GA4513@auslistsprd01.us.dell.com> <87zlnzb8ce.fsf@rho.meyering.net> <20080730172922.GA20191@auslistsprd01.us.dell.com> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.11; x86_64-redhat-linux-gnu) Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1036 Lines: 23 > read/modify/write. T10 and T13 are looking to add commands to > expose this different underlying physical sector size so the OS > could be aware of it. This is primarily being driven to mitigate The identify bits are already there for reporting both size and offset. > 3) those that report a 4096-byte sector size, and are really a > 4096-byte size. This seems ideal for aware OSs. > > Which of 2) or 3) hit the market in mass remains to be seen. I want > Linux to be able to handle either painlessly. I am expecting 3 to turn up some _minor_ problem cases. Many older ATA controllers magically know the sector size of media and the internal state machines and FIFO they use for performance is potentially going to go gaga in this case when we do a PIO transfer. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/