![]() | |||||||||||||
Messages in this thread |
Jens Axboe wrote: > So you could change ->max_sectors to be 'max allowable io, hardware > limitation' and add ->optimal_sectors to be 'best sized io'. I don't see > tha it buys you anything, since you'd be going for optimal_sectors all > the time anyways. In terms of implementation, I imagine we would add a ->max_hw_sectors, once the IO scheduler and VM (or userland?) are smart enough to tune ->max_sectors dynamically. 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 14:02 [from the cache] ©2003-2008 | |||||||||||||