Linked by Thom Holwerda on Wed 10th Jun 2009 09:46 UTC, submitted by RJop
Linux Linus Torvalds has announced the release of version 2.6.30 of the Linux kernel. "I'm sure we've missed something, and I know we have some regressions pending. At the same time, we do need the coverage of a eral release, and on the whole it looks pretty good. We've fixed a few regressions in the last few days, and there's always 2.6.30.x." The list of changes is interesting.
Thread beginning with comment 367710
To read all comments associated with this story, please click here.
kernel regression
by Andre4s on Wed 10th Jun 2009 10:59 UTC
Member since:

What does kernel regression mean?

Reply Score: 1

RE: kernel regression
by WereCatf on Wed 10th Jun 2009 11:02 in reply to "kernel regression"
WereCatf Member since:

It means that a feature that worked in the last release will exhibit buggy or completely broken behaviour now.

Reply Parent Score: 4

RE: kernel regression
by _xmv on Wed 10th Jun 2009 12:11 in reply to "kernel regression"
_xmv Member since:

What does kernel regression mean?

its a nice way to say "bug"

(yes yes, its a specific kind of bug: feature that worked before stopped working, effectively "regressing")

Reply Parent Score: 1

RE[2]: kernel regression
by meeh on Wed 10th Jun 2009 13:22 in reply to "RE: kernel regression"
meeh Member since:

"bug" is too ambigious, regression is when functionality gets worse.

I belive in this case the topic is performance regression, which means that while new features was added or other modules/features got optimised one or more existing features got slower , eg uses more cpu cycles to achieve the same work.

Common regressions happens while eg. choosing to optimise towards either latency or throughput, you rarely get to satisfy all users in such a case, which could explain why just about every important module is hot-plugable in the Linux kernel (eg. schedulers optimized for servers vs desktops).

Reply Parent Score: 1