On Mon, Nov 02, 2009 at 08:29:08AM -0500, Martin K. Petersen wrote: > Similarly, nothing prevents you from submitting a misaligned unmap > request. If you do, the array will just ignore the portions that do not > constitute entire allocation units. Your code is taking what is a hint > and turning it into a hard limit. Note that it's called OPTIMAL UNMAP > GRANULARITY, not REQUIRED UNMAP GRANULARITY. > > Every vendor I have talked to have asked us to always unmap the *entire* > LBA range we're interested in freeing. No exceptions. > > We don't throw away the beginning/end of a read/write request because > it's not properly aligned either, do we? read/write is different. If we throw parts of it away we lose data, we don't do for unmap requests. I'll resend a patch series that moves the trimming of the range into sd.c as suggested later and make it tunable. That might not be what we want to keep long term, but it'll allow us benchmarking both variants on the real life arrays. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
