[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110928.134207.174306348033999091.davem@redhat.com>
Date: Wed, 28 Sep 2011 13:42:07 -0400 (EDT)
From: David Miller <davem@...hat.com>
To: akpm@...gle.com
Cc: netdev@...r.kernel.org, vzapolskiy@...il.com, zbr@...emap.net
Subject: Re: [patch 1/1] connector: add comm change event report to proc
connector
From: akpm@...gle.com
Date: Wed, 21 Sep 2011 12:26:44 -0700
> From: Vladimir Zapolskiy <vzapolskiy@...il.com>
> Subject: connector: add comm change event report to proc connector
>
> Add an event to monitor comm value changes of tasks. Such an event
> becomes vital, if someone desires to control threads of a process in
> different manner.
>
> A natural characteristic of threads is its comm value, and helpfully
> application developers have an opportunity to change it in runtime.
> Reporting about such events via proc connector allows to fine-grain
> monitoring and control potentials, for instance a process control daemon
> listening to proc connector and following comm value policies can place
> specific threads to assigned cgroup partitions.
>
> It might be possible to achieve a pale partial one-shot likeness without
> this update, if an application changes comm value of a thread generator
> task beforehand, then a new thread is cloned, and after that proc
> connector listener gets the fork event and reads new thread's comm value
> from procfs stat file, but this change visibly simplifies and extends the
> matter.
>
> Signed-off-by: Vladimir Zapolskiy <vzapolskiy@...il.com>
> Acked-by: Evgeniy Polyakov <zbr@...emap.net>
> Cc: David Miller <davem@...emloft.net>
> Signed-off-by: Andrew Morton <akpm@...gle.com>
Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists