Live data from Hacker News

Linux 3.4 kernel released

kernelnewbies.org

31–40 of 47 posts

Re: Linux 3.4 kernel released

#31
post #24

What I thought was more interesting (Linus noted "Nothing really exciting happened since -rc7...") was the exchange between Linus and Peter Zijlstra, in particular this Linus eruption: https://lkml.org/lkml/2012/5/19/97

> And I *do* know that the real world simply isn't simple enough that we could > ever do a perfect job, so don't even try - instead aim for "understandable, > maintainable, and gets the main issues roughly right". It's striking that his manner is blunt and over-general... and his technical content is also blunt and over-general. He's known for his pragmatic and effective engineering decisions.

Found this article citing Peter on NUMA scheduling in March:

Toward better NUMA scheduling http://lwn.net/Articles/486858/

Peter's cited email: http://lwn.net/Articles/486850/

Actually, in reviewing the data, it seems this issue has been around for a long time, and could be the root of Linus's irritation in the first place. Perhaps he feels no headway is being made for such a long time, even the smallest perceived misstep sets him off.

If nothing else, I would love to actually see some technically detailed papers come out of this that get to the root of the problem, propose solutions to it, and identify what of those solutions are being tested and when they are expected to be implemented. Nothing like a good argument between engineers to get a root cause rooted out and a solution in place.

Re: Linux 3.4 kernel released

#32

What I thought was more interesting (Linus noted "Nothing really exciting happened since -rc7...") was the exchange between Linus and Peter Zijlstra, in particular this Linus eruption: https://lkml.org/lkml/2012/5/19/97

not everyone agrees with linus. ingo molnar supported peter zijlstra. with facts. something linus always wants but usually is too busy delivering (ehem..).

"the result of these commits is: 24 files changed, 417 insertions(+), 975 deletions(-)

Most of the linecount win is due to the removal of the dysfunctional power scheduling - but even without that commit it's a simplification:

15 files changed, 415 insertions(+), 481 deletions(-)

while it lifts the historic limitations of the sched-domains approach and makes the code a whole lot more logical."

Re: Linux 3.4 kernel released

#33
post #3

The X32 ABI is interesting. Who'd have thought this many years after 64 bit becoming mainstream, (and decades after it becoming mainstream on servers) something like this would be needed.

SGI's IRIX always had the ability to do since decades ago. Of course, like others have stated, the main reason is to conserve both memory (for pointers) and more importantly bus bandwidth (which is a mayor problem in MPI/SMP systems memory, especially in those IRIX supported with 128+ cpus in a NUMA configuration).

There are still many features where linux is just playing catch-up that commercial unix kernels had decades ago.

Re: Linux 3.4 kernel released

#34

I'm confused. Is 3.x meant for a different class of system, or are distros like Ubuntu intentionally lagging behind in 2.6.x land?

Latest Ubuntu has kernel version 3.2. What distros are still on 2.6?

Debian Stable of course!

Re: Linux 3.4 kernel released

#37

I'm confused. Is 3.x meant for a different class of system, or are distros like Ubuntu intentionally lagging behind in 2.6.x land?

There is no 'major version jump' difference between the two. The reasoning was simply "2.40 is getting unwieldy as a number, so I'm going to start 3.0 here".

Re: Linux 3.4 kernel released

#40
"...making slow start suboptimal" caught my eye, but I didn't understand the rest. Is this for a specific circumstance or general? Did they find something better than slow start or did they break it, causing it to be suboptimal?
Post reply on HN