Vladimir Zapolskiy f786ecba41 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@gmail.com> Acked-by: Evgeniy Polyakov <zbr@ioremap.net> Cc: David Miller <davem@davemloft.net> Signed-off-by: Andrew Morton <akpm@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2011-09-28 13:41:50 -04:00
..
cn_proc.c	connector: add comm change event report to proc connector	2011-09-28 13:41:50 -04:00
cn_queue.c	connector: convert to synchronous netlink message processing	2011-03-30 17:14:33 -07:00
connector.c	Connector: Correctly set the error code in case of success when dispatching receive callbacks	2011-06-07 12:02:00 -07:00
Kconfig	trivial: Kconfig: .ko is normally not included in module names	2009-06-12 18:01:50 +02:00
Makefile