On 04/11/2010 06:52 PM, Linus Torvalds wrote:
On Sun, 11 Apr 2010, Avi Kivity wrote:
And yet Oracle and java have options to use large pages, and we know google
and HPC like 'em. Maybe they just haven't noticed the fundamental brokenness
yet.
The thing is, what you are advocating is what traditional UNIX did.
Prioritizing the special cases rather than the generic workloads.
And I'm telling you, it's wrong. Traditional Unix is dead, and it's dead
exactly _because_ it prioritized those kinds of loads.
This is not a specialized workload. Plenty of sites are running java,
plenty of sites are running Oracle (though that won't benefit from
anonymous hugepages), and plenty of sites are running virtualization.
Not everyone does two kernel builds before breakfast.
I'm perfectly happy to take specialized workloads into account, but it
needs to help the _normal_ case too. Somebody mentioned 4k CPU support as
an example, and that's a good example. The only reason we support 4k CPU's
is that the code was made clean enough to work with them and actually
help clean up the SMP code in general.
I've also seen Andrea talk about how it's all rock solid. We _know_ that
is wrong, because the anon_vma bug is not solved. That bug apparently
happens under low-memory situations, so clearly nobody has really stressed
the low-memory case.
Well, nothing is rock solid until it's had a few months in the hands of
users.
So here's the deal: make the code cleaner, and it's fine. And stop trying
to sell it with _crap_.
That's perfectly reasonable.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>