Re: Implementing NVMHCI...

[Pavel Machek <pavel@ucw.cz>]

Hi!

>> Well, no one is talking about 64KB granularity for in-core files.  Like 
>> you noticed, Windows uses the mmu page size.  We could keep doing that, 
>> and still have 16KB+ sector sizes.  It just means a RMW if you don't  
>> happen to have the adjoining clean pages in cache.
>>
>> Sure, on a rotating disk that's a disaster, but we're talking SSD here, 
>> so while you're doubling your access time, you're doubling a fairly  
>> small quantity.  The controller would do the same if it exposed smaller 
>> sectors, so there's no huge loss.
>>
>> We still lose on disk storage efficiency, but I'm guessing that a 
>> modern tree with some object files with debug information and a .git 
>> directory it won't be such a great hit.  For more mainstream uses, it 
>> would be negligible.
>
>
> Speaking of RMW...    in one sense, we have to deal with RMW anyway.  
> Upcoming ATA hard drives will be configured with a normal 512b sector  
> API interface, but underlying physical sector size is 1k or 4k.
>
> The disk performs the RMW for us, but we must be aware of physical  
> sector size in order to determine proper alignment of on-disk data, to  
> minimize RMW cycles.

Also... RMW hsa some nasty reliability implications. If we use 1KB
block size ext3 (or something like that), unrelated data may now be
damaged during powerfail. Filesystems can not handle that :-(.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html