jim owens wrote:
Bill Davidsen wrote:
I assume that it really is artificial, rather than the device really
being ready for another operation (other than another TRIM). I lack
the hardware, but the test would be the time to complete a read, trim
and read, and two trim and read operations. Just my thought that the
TRIM in progress may only block the next TRIM, rather than other
operations.
I don't know his test sequence but READ is not the likely command
before and after TRIM unless we are talking about TRIM being issued
only in delayed host garbage collection. Filesystems send WRITES
during delete.
My idea is to test using a command which will definitely not need to
prepare the media before completion, thus read. If TRIM doesn't block
reads, then NCQ may allow reads to take place. Because of buffering slow
reads hurt more than slow writes in terms of user perception.
--
bill davidsen <davidsen@xxxxxxx>
CTO TMR Associates, Inc
"You are disgraced professional losers. And by the way, give us our money back."
- Representative Earl Pomeroy, Democrat of North Dakota
on the A.I.G. executives who were paid bonuses after a federal bailout.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
