Hi Leenart,
> Dhaval Giani pointed out to me that the same can be done from userspace
> simply by creating a cgroup for each session in the cpu hierarchy. Turns
> simply by creating a cgroup for each session in the cpu hierarchy. Turns
So a session's (as you're referring) initiator to would be the terminal emulator process that has a virtual tty and systemd detect those and setup a proper cgroup so that we could differentiate when scheduling with other processes?
-Ilyes
On Tue, Nov 16, 2010 at 6:14 PM, Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote:
This appears completely backwards to me. Attaching things like this to aOn Tue, 16.11.10 16:58, Ilyes Gouta (ilyes.gouta@xxxxxxxxx) wrote:
> 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? :)
TTY is just wrong, because normally we don't have a single TTY around on
most graphical sessions.
The kernel doesn't really have a notion of what a "session" is (only the
audit subsystem kinda has), but if this grouping behaviour is supposed
to be bound to a session, then attaching it to a TTY is a pretty shitty
replacement.
Dhaval Giani pointed out to me that the same can be done from userspace
simply by creating a cgroup for each session in the cpu hierarchy. Turns
out systemd actually does pretty much that, except in the named systemd
hierarchy. It is trivial modification to create a group in both hierarchies.
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
