summaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorVladimir Zapolskiy <vzapolskiy@gmail.com>2011-09-21 09:26:44 +0000
committerDavid S. Miller <davem@davemloft.net>2011-09-28 13:41:50 -0400
commitf786ecba4158880f8cdc0ebb93e7d78e6c125449 (patch)
tree0291e9079912f41ad2dd67ffd609a554e98b7850 /Kconfig
parent5dd17e08f333cde0fa11000792e33d8d39b5599f (diff)
downloadop-kernel-dev-f786ecba4158880f8cdc0ebb93e7d78e6c125449.zip
op-kernel-dev-f786ecba4158880f8cdc0ebb93e7d78e6c125449.tar.gz
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>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud