Re: Why is NCQ enabled by default by libata? (2.6.20)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Justin Piszcz
Date: Tuesday, March 27, 2007 - 9:25 am

On Tue, 27 Mar 2007, linux@horizon.com 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 :)

Also you are disabling NCQ on/off via the /sys/block device, e.g., setting 
it to 1 (off) and 31 (on) during testing, yes?

Justin.
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Why is NCQ enabled by default by libata? (2.6.20), Justin Piszcz, (Tue Mar 27, 9:25 am)
Re: Why is NCQ enabled by default by libata? (2.6.20), Phillip Susi, (Wed Mar 28, 7:42 am)
Re: Why is NCQ enabled by default by libata? (2.6.20), Jeff Garzik, (Wed Mar 28, 7:48 am)
Re: Why is NCQ enabled by default by libata? (2.6.20), Phillip Susi, (Thu Mar 29, 10:28 am)
Re: Why is NCQ enabled by default by libata? (2.6.20), Jeff Garzik, (Thu Mar 29, 11:51 am)
RE: Why is NCQ enabled by default by libata? (2.6.20), David Schwartz, (Thu Mar 29, 2:47 pm)
Re: Why is NCQ enabled by default by libata? (2.6.20), Lennart Sorensen, (Fri Mar 30, 9:33 am)