In fact it results in "everybody" just having the distro defaults, which
in some cases then depend on things like which particular version they
initially installed things with (because some decisions end up being
codified in long-term memory by that initial install - like the size of
the journal when you mkfs'd your filesystem, or the alignment of your
partitions, or whatever).
The exception, of course, ends up being power-users that then tweak things
on their own.
Me, I may be a power user, but I absolutely refuse to touch default
values. If they are wrong, they should be fixed. I don't want to add
"relatime" to my /etc/fstab, because then the next time I install, I'll
forget - and if I really need to do that, then the kernel should have
already done it for me as the default choice.
I also don't want to say that "Fedora should just do it right" (I'll
complain about things Fedora does badly, but not setting magic values in
/proc is not one of them), because then even if Fedora _were_ to get
things right, others won't. Or even worse, somebody will point that SuSE
or Ubuntu _did_ do it right, but the distro I happen to use is doing the
wrong thing.
And yes, I could do my own site-specific tweaks, but again, why should I?
If the tweak really is needed, I should put it in the generic kernel. I
don't do anything odd.
End result: regardless of scenario, depending on user-land tweaking is
always the wrong thing. It's the wrong thing for distributions (they'd all
need to do the exact same thing anyway, or chaos reigns, so it might as
well be a kernel default), and it's the wrong thing for individuals
(because 99.9% of individuals won't know what to do, and the remaining
0.1% should be trying to improve _other_ peoples experiences, not just
their own!).
The only excuse _ever_ for user-land tweaking is if you do something
really odd. Say that you want to get the absolutely best OLTP numbers you
can possibly get - with no regards for _any_ other workload. In that case,
you want to tweak the numbers for that exact load, and the exact machine
that runs it - and the result is going to be a totally worthless number
(since it's just benchmarketing and doesn't actually reflect any real
world scenario), but hey, that's what benchmarketing is all about.
Or say that you really are a very embedded environment, with a very
specific load. A router, a cellphone, a base station, whatever - you do
one thing, and you're not trying to be a general purpose machine. Then you
can tweak for that load. But not otherwise.
If you don't have any magical odd special workloads, you shouldn't need to
tweak a single kernel knob. Because if you need to, then the kernel is
doing something wrong to begin with.
Linus
--
