From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: Implementing NVMHCI... Date: Sat, 11 Apr 2009 16:21:26 -0400 Message-ID: <49E0FBC6.3050600@garzik.org> References: <49E0D47B.9070205@garzik.org> <20090411203246.513a0892@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:38105 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754601AbZDKUWB (ORCPT ); Sat, 11 Apr 2009 16:22:01 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Linus Torvalds Cc: Alan Cox , Linux IDE mailing list , LKML , Jens Axboe , Arjan van de Ven Linus Torvalds wrote: > > On Sat, 11 Apr 2009, Alan Cox wrote: >>> The spec describes the sector size as >>> "512, 1k, 2k, 4k, 8k, etc." It will be interesting to reach >>> "etc" territory. >> Over 4K will be fun. > > And by "fun", you mean "irrelevant". > > If anybody does that, they'll simply not work. And it's not worth it even > trying to handle it. FSVO trying to handle... At the driver level, it would be easy to clamp sector size to 4k, and point the scatterlist to a zero-filled region for the >4k portion of each sector. Inefficient, sure, but it is low-cost to the driver and gives the user something other than a brick. if (too_large_sector_size) nvmhci_fill_sg_clamped_interleave() else nvmhci_fill_sg() Regards, Jeff