Linked by Thom Holwerda on Mon 20th Jul 2009 19:16 UTC
Permalink for comment 374722
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
More News »
Sponsored Links



Member since:
2008-12-26
In my view, this is non optimal behavior from Linux:
http://opsmonkey.blogspot.com/2007/01/linux-memory-overcommit.html
...
Linux over allocates RAM.
...
Maybe this has something to do with the declining quality of the Linux code? Linux kernel hacker Andrew Morton explains:
...
Or this thread:
http://kerneltrap.org/Linux/Active_Merge_Windows
"the [Linux source] tree breaks every day, and it's becoming an extremely non-fun environment to work in. We need to slow down the merging, we need to review things more, we need people to test their [...] changes!"
...
I think it has something to do with Linux not having stable ABIs?
...
And
http://www.enterprisestorageforum.com/sans/features/article.php/374...
Quite extensive troll collection you have there.