Slashdot Mirror
Improve Your GNU/Linux Experience With -mm Patches
An anonymous reader writes "Anyone interested in squeezing maximum performance out of their GNU/Linux operating system and willing to compile a new kernel will be interested in this KernelTrap article about Andrew Morton's -mm patchset. The patchset currently offers better stability and performance than the mainline 2.6.0-test kernel, as well as containing numerous functionality enhancements. Much of the additional functionality is described, as well as providing simple step by step installation instructions. Reading this article, one can certainly understand why Linux creator Linus Torvalds has chosen Andrew to soon become the 2.6 maintainer."
I've been using the -mm patchset since 2.5.4x and have been very happy with it. Since it includes the Interactivity patches from Con Kolivas it kicks ass on your desktop, too. Even moreso than the 2.4.x-ck series of patches, which are intended for desktop use. Do note however that it is sometimes more experimental in nature than the mainline kernel, since new functionality is often tested out there first.
m /patches/2.6/
If you know how to patch your kernel already, you don't need to read the article, get the patch for your kernel here: http://ftp.kernel.org/pub/linux/kernel/people/akp
* Several monkeys are here, playing banjos and wearing small hats.
The mm patch is the only reason I use 2.6 on my laptop since it provides the synaptics touchpad support. Yes, I was able to use an external mouse without the patch, but the idea of not being able to use the built in touchpad was really annoying.
Does anyone know why touchpad support is not included in the default 2.6 tree?
Yes, most of his stuff will make it into mainline, and in fact most of the things which have been tested out in -mm have already made it into mainline (hence why the -mm patchset doesn't increase in size constantly). The more experimental things stay behind until they are acceptable, and then he pushes them to Linus. Works well :-)
* Several monkeys are here, playing banjos and wearing small hats.
So XFS users should probably go with -mm2 for now.
* Several monkeys are here, playing banjos and wearing small hats.
Yeah, let's call it "deb and ian" or something like that.
What's stopping me from becoming the Linux 2.6 kernel maintainer?
The fact that you keep trolling on Slashdot, perhaps?
patchset currently offers better stability and performance than the mainline 2.6.0-test kernel So if these stability and performance patches are so great as the article says, why aren't they in the main kernel already? Does Linus just not like them??
Switching to Linux can be an adventure!
Also posted on OSNews:
I've tested the 2.6.0-test5 kernel with Con Kolivas' interactivity patch. I've also tested Con's 2.4.21 and 2.4.22 patches and so far nothing can match the gentoo-sources-2.4.20-r5-aavm patch for speed. (I'm using Mandrake 9.1 and GCC 3.3.1, BTW.) Just watching the init scripts running at bootup and how long XFree86 and Mozilla Firebird take to launch, there's no comparison. Considering that this patch uses Con's performance enhancements, I'm not too confident that it can do any better. But maybe I'll test it out and see what it can do.
If anyone is interested in a mini-howto on using the gentoo-sources patch, speak up and I'll try to whip something up.
> Hmm.. I thought Linux was open source and anyone could damn well do what they please with it. What's stopping me from becoming the Linux 2.6 kernel maintainer?
Nothing at all is stopping you from becoming a 2.6 kernel maintainer, in the same way that Alan Cox, Dave Jones et al maintain well-respected 'unofficial', but important, variations on the 2.4 tree. You set up a 2.6 tree, incorporate patches that strike you as being particularly useful, and who knows? - others may feel the same, and your tree (and you!) get to the same point as a dj or mm tree.
No, yours won't be the 'official' (ie, the reference) 2.6 tree - just because you set up a 2.6 tree doesn't obligate Linus or his designated maintainer from accepting your patches - but neither can they/do they/would they prevent others from using your tree if they prove useful, and if your particular patch set does prove widely useful, you've got a good shot at getting them included in the main reference tree.
And, the more variations on a given kernel tree, the better. They're excellent labs for trying out things that the reference tree maintainers may not want to try just yet, and give good alternative kernel sources for those not up to such an ongoing project. So yes, I'd recommend you do exactly as you seem to be suggesting, and set up and maintain a 2.6 tree with whatever patch set you feel worthwhile.
It's a satisfying feeling to see your machine crash with the highest performance possible.