News for hackers. Stuff that matters.
Re:The ~200 Line Linux Kernel Patch That Does Wonders by leif on Tuesday November 16, 2010 @11:49AM (#1910658)
There isn't one. It's an existing option in the kernel, you can configure cgroups that way already, but most people don't do this so the feature is wasted. All this patch does is roughly approximate a decent-looking cgroup configuration by splitting processes by tty automatically.
Re:The ~200 Line Linux Kernel Patch That Does Wonders by astrange on Tuesday November 16, 2010 @06:01PM (#1912097)
Of course there will be a regression if you change the scheduler policy. ck tried something similar to this and mplayer performance suffered with it (though I don't remember the details). It also broke gnome-startup because it assumed some specific schedule ordering, though this patch is more limited so it might not.
Re:The ~200 Line Linux Kernel Patch That Does Wonders by leif on Tuesday November 16, 2010 @07:51PM (#1912437)
When your application breaks because of scheduler ordering, You're Doing It Wrong.
Re:The ~200 Line Linux Kernel Patch That Does Wonders by astrange on Wednesday November 17, 2010 @05:38PM (#1916045)
Yeah, well, kernels need to support existing programs…

By the way, your post is the single most obvious statement I've read this year. You got upvoted just because you capitalized some words?

Re:The ~200 Line Linux Kernel Patch That Does Wonders by leif on Thursday November 18, 2010 @02:24AM (#1917162)
I got upvoted because I'm right. Kernels don't need to support horribly designed programs just because they exist, just like they don't need to support horribly designed programs that don't exist yet. Kernels support an interface and that's it. If you write code that abuses the interface, get ready to become a regression, and that'll be your own fault.

(TBH I have no idea why I got upvoted, it wasn't that insightful, but I stick by what I said)

(EDIT: I'm talking about gnome-startup. That's a stupid regression that never should've happened. The mplayer performance bug is totally understandable if you're mucking with the scheduler. What we really need is for someone (distros?) to pick up cgroups and provide a nice UI for it, some sane but nondestructive defaults, etc. Until then, this is a nice patch that keeps badly behaving programs from dragging down the entire system. At the very least, we mostly get user separation in multi-user environments.)