Messages in this thread | | | Date | Wed, 28 Mar 2007 10:48:51 -0400 | From | Jeff Garzik <> | Subject | Re: Why is NCQ enabled by default by libata? (2.6.20) |
| |
Phillip Susi wrote: > Justin Piszcz wrote: >> I would try with write-caching enabled. >> Also, the RAID5/RAID10 you mention seems like each volume is on part of >> the platter, a strange setup you got there :) > > Shouldn't NCQ only help write performance if write caching is > _disabled_? Since write cache essentially is just non tagged command > queuing?
NCQ provides for a more asynchronous flow. It helps greatly with reads (of which most are, by nature, synchronous at the app level) from multiple threads or apps. It helps with writes, even with write cache on, by allowing multiple commands to be submitted and/or retired at the same time.
Jeff
- 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/
| |