Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759234AbZDKVtV (ORCPT ); Sat, 11 Apr 2009 17:49:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758192AbZDKVtI (ORCPT ); Sat, 11 Apr 2009 17:49:08 -0400 Received: from smtp-out.google.com ([216.239.45.13]:46076 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757448AbZDKVtH convert rfc822-to-8bit (ORCPT ); Sat, 11 Apr 2009 17:49:07 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=qsUDz8XSs3h+t9BzR5CjFKjTBXD+Hy+dzq0IqEktg1qB3uUK2JJM78wuiDoL+r8po mqH7Z9FWqMM9mk0sEyEsQ== MIME-Version: 1.0 In-Reply-To: References: <49E0D47B.9070205@garzik.org> <20090411203246.513a0892@lxorguk.ukuu.org.uk> Date: Sat, 11 Apr 2009 14:49:02 -0700 Message-ID: Subject: Re: Implementing NVMHCI... From: Grant Grundler To: Linus Torvalds Cc: Alan Cox , Jeff Garzik , Linux IDE mailing list , LKML , Jens Axboe , Arjan van de Ven Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1761 Lines: 52 On Sat, Apr 11, 2009 at 12:52 PM, 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. Why does it matter what the sector size is? I'm failing to see what the fuss is about. We've abstract the DMA mapping/SG list handling enough that the block size should make no more difference than it does for the MTU size of a network. And the linux VM does handle bigger than 4k pages (several architectures have implemented it) - even if x86 only supports 4k as base page size. Block size just defines the granularity of the device's address space in the same way the VM base page size defines the Virtual address space. > That said, I'm pretty certain Windows has the same 4k issue, so we can > hope nobody will ever do that kind of idiotically broken hardware. Of > course, hardware people often do incredibly stupid things, so no > guarantees. That's just flame-bait. Not touching that. thanks, grant > >                Linus > -- > To unsubscribe from this list: send the line "unsubscribe linux-ide" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at  http://vger.kernel.org/majordomo-info.html > -- 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/