David Woodhouse wrote:
On Thu, 6 Nov 2008, James Bottomley wrote:
The way to do this properly would be to run a chequerboard of partials,
but this would effectively have trim region tracking done in the block
layer ... is this worth it?
By the way, the latest (from 2 days ago) version of the Thin
Provisioning proposal is here:
http://www.t10.org/ftp/t10/document.08/08-149r4.pdf
I skimmed it but don't see any update implying that trim might be
ineffective if we align wrongly ... where is this?
I think we should be content to declare such devices 'broken'.
They have to keep track of individual sectors _anyway_, and dropping
information for small discard requests is just careless.
Big arrays have an internal "track" size that is much larger than 512
bytes (Symm for example is 64k. Everything smaller than that is a
read-modify-write. Effectively, they have few to no bits left to track
this other bit of state at the smal level of granularity.
The thing that makes this even more twisted is that the erase/unmap
chunk size is a multiple of the internal size (which would already be an
issue :-))
Ric
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
