lkml.org 
[lkml]   [2009]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Implementing NVMHCI...
Avi Kivity wrote:
> Jeff Garzik wrote:
>>>> (c) export information indicating the true sector size, in a manner
>>>> similar to how the ATA driver passes that info to userland
>>>> partitioning tools.
>>>
>>> Eventually we'll want to allow filesystems to make use of the native
>>> sector size.
>>
>> At the kernel level, you mean?
>>
>
> Yes. You'll want to align extents and I/O requests on that boundary.

Sure. And RAID today presents these issues to the filesystem...

man mke2fs(8), and look at extended options 'stride' and 'stripe-width'.
It includes mention of RMW issues.


>> But if you are talking about filesystems directly supporting sector
>> sizes >4kb, well, I'll let Linus and others settle that debate :) I
>> will just write the driver once the dust settles...
>
> IMO drivers should expose whatever sector size the device have,
> filesystems should expose their block size, and the block layer should
> correct any impedance mismatches by doing RMW.
>
> Unfortunately, sector size > fs block size means a lot of pointless
> locking for the RMW, so if large sector sizes take off, we'll have to
> adjust filesystems to use larger block sizes.

Don't forget the case where the device does RMW for you, and does not
permit direct access to physical sector size (all operations are in
terms of logical sector size).

Jeff





\
 
 \ /
  Last update: 2009-04-14 14:25    [from the cache]
©2003-2011 Jasper Spaans