![]() | |||||||||||||
Messages in this thread |
Jeff Garzik wrote: > It's up to the sysadmin to choose a disk scheduling policy they like, > which implies that a _scheduler_, not each individual driver, should > place policy limitations on max_sectors. <tangent> The block layer / scheduler guys should also think about a general (not SCSI specific) way to tune TCQ tag depth. That's IMO another policy decision. I'm about to add a raft of SATA-2 hardware, all of which are queued. The standard depth is 32, but one board supports a whopping depth of 256. Given past discussion on the topic, you probably don't want to queue 256 requests at a time to hardware :) But the sysadmin should be allowed to, if they wish... 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/ | ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||