On Fri, Aug 25, 2006 at 12:37:54PM +0200, Adrian Bunk wrote: > On Fri, Aug 25, 2006 at 08:07:37AM +0200, Jan Engelhardt wrote: > > > > > >There's e.g. no reason to ask all users whether they want to compile all > > >I/O schedulers into their kernel. > > > > > The users that do not know how to handle it should not be compiling a > > kernel. If in doubt, they should read the help texts and follow the "If > > unsure" clause listed there. > > If your distribution ships 2.6.x and your hardware is not supported > before 2.6.x+1 you need your own kernel. > > The expectation "only kernel hackers don't use distribution kernels" is > wrong in too many cases. > > "System administrator" is a target audience of the kernel configuration, > and we should make it as easy as possible for such people to compile > their own kernel. This is solvable with good help texts. config IOSCHED_PRON tristate The pr0n I/O scheduler is specifically tuned for one specific task -- busy webserver shipping pr0n to customers. Distributions of file sizes and access patterns were heavily analyzed during development. To make such server even more faster also select "pr0n filesystem support" in File systems menu and read help text there. If you aren't in pr0n industry, say N. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
