Three Things That Won't Be In The Linux 2.6.37 Kernel

[phoronix]

Phoronix: Three Things That Won't Be In The Linux 2.6.37 Kernel

While the Linux 2.6.36 kernel was released yesterday, we already have our eyes towards the Linux 2.6.37 kernel to see what new features this next kernel will bring, any performance changes that may come as a result (we continue to benchmark the kernel everyday), and this will likely be the kernel version used by Ubuntu 11.04 and other early 2011 Linux distributions. While we have already reported on some of the features that should be merged into the Linux 2.6.37 kernel, there's at least three major features we have been looking forward to that will be sadly missing from this kernel...

http://www.phoronix.com/vr.php?view=ODY5OQ

[Jimbo]

Yeah! nice! via drivers and poulsbo-shit , although there is a more important event on 2.6.37, Nick Piggin VFS scalability patches are probably get totally merged, since now only a few of required patches merged, but full functionality would be achieved on 2.6.37. This guy, other FS develoveper, and linux too, are working on this since 2009. One of the weak point of linux is scalability on multicore system and this is going to finally be addressed.

http://lwn.net/Articles/360199/

http://lwn.net/Articles/401738/

[Jimbo]

http://lkml.org/lkml/2010/7/22/417

[sirdilznik]

Reiser4 is never going to be included in the mainline kernel. It's something that's just never going to happen... like HURD.

[bash]

... like HURD.

But at least the name is great for lame jokes, like "You're in a world of HURD now!".

[hax0r]

This article and posts make me sad . Maybe BFS scheduler will finally get merged. Let's hope the VFS patches will make it too, along with dekstop responsiveness patches that didn't make into 2.6.36.

[rohcQaH]

Three things not going in, all three not surprising at all.

VIA's silence is quite clear. Nobody expects a ninja-code drop during a merge-window with no prior activity, announcements or public reviews.

Reiser4 is an ongoing heap of problems and there is not enough interest in getting it merged, anyway.

Did anyone really expect HD6000 support? AMD is reducing the time between launch and OSS support, but expecting it to jump from 5 to 11 months (depending on the feature-set) to -1 week is wishful thinking at best.


I also doubt BFS will be merged anytime soon, since it's slower in many common workloads.

[pejakm]

I would also like to see BFQ I/O scheduler merged.

[Kjella]

VIA's silence is quite clear. Nobody expects a ninja-code drop during a merge-window with no prior activity, announcements or public reviews.

Did anyone really expect HD6000 support? AMD is reducing the time between launch and OSS support, but expecting it to jump from 5 to 11 months (depending on the feature-set) to -1 week is wishful thinking at best.

Well AMD could have had working support under NDA and done a "ninja code drop" today that maybe Linus would have allowed for RC1. It's probably easier to get open source support brought up around the same time as release than coming many months later trying to recover it from old docs people don't remember well anymore. But yeah, 2.6.38 is more likely...

[SarahKH]

Three things not going in, all three not surprising at all.

VIA's silence is quite clear. Nobody expects a ninja-code drop during a merge-window with no prior activity, announcements or public reviews.

Lets be honest nobody actually expects anything from VIA. They've pretty much done press releases and just enough effort to stamp "open source supporting company" on stuff.