Of course there's no gain on writes with write cache enabled, that is
obvious:
It is nearly impossible for a drive to cache random reads, therefore they
have the greatest performance penalty due to seeks and rotational latency.
That is why queueing improves random reads so much.
Repetitive and Sequential reads should see no benefit at all from queueing,
since the virtually-zero-size drive cache actually hits its locality
(spatial or temporal) cases for these commands.
Similarly, any write with the drive's write cache enabled will see zero or
near-zero benefit from queueing writes. The only reason to use queued
writes is so you can intermingle them with queued reads without flushing
your tags.
If you disable write cache on the drive (Journalling/RAID environments) then
you'll see performance nearly identical to reads, which then can benefit by
queueing to the same degree.
>Still it is a lame protocol.
I don't necessarilly disagree, however I'm not on T13 and didn't have any
input.
--eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/