Re: [PATCH] connector: add comm change event report to procconnector

[Andrew Morton]

On Tue,  2 Aug 2011 21:46:51 +0300
Vladimir Zapolskiy <vzapolskiy@xxxxxxxxx> wrote:

> This change adds 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.

Monotoring and controlling tasks via their comm value seems weird,
inefficient and unreliable.  Who is doing this, and why?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/