Hi,
I've been readingÂhttp://lkml.org/lkml/2010/11/16/402Âand actually Lennart has put some solid thoughts and arguments there and IMHO it was *somehow* pretty convincing that this should be done at user-space, in conjunction with tools such as systemd, albeit introducing more complexity in form of configuration infrastructure and whatnot.
Having this being done automatically by the kernel looks really easy and yet promising. The downside of it is that it just feels like it's something rigged towards a special class of applications (TTY based, build jobs) and would actÂbehind the scene without user-space knowing (explicitly) about this classification, cgroups being spawned and subtasks associated to them.
Still, It would be nice to have this differentiation in place, being implemented in either forms, since it brings a certain win for the desktop user and developer. I think having a term open for churning code is part (or a possible user-case) of the desktop experience :)
-Ilyes
2010/11/17 MichaÅ Piotrowski <mkkp4x4@xxxxxxxxx>
Hi,
2010/11/16 Ilyes Gouta <ilyes.gouta@xxxxxxxxx>:
Let me guess - Canonical already announced (or will do so within the> Hi,
> http://linux.slashdot.org/story/10/11/16/1330233/The-200-Line-Linux-Kernel-Patch-That-Does-Wonders
> patch:Âhttp://marc.info/?l=linux-kernel&m=128978361700898&w=2
> Can we have this patch back ported into the current kernel for Fedora 14 and
> possibly posted as an update? :)
next few hours) that they will use this patch in the new Ubuntu :)
> Would be wonderful!
Surely this would be
> -Ilyes
> --
> devel mailing listBest regards,
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
Michal
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
