From: Nikiforov Alex <a.nikiforov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Kyungmin Park
<kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
Dmitry Solodkiy
<d.solodkiy-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
a.nikiforov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
Subject: [RFC] event about group change
Date: Fri, 23 Mar 2012 10:02:41 +0400 [thread overview]
Message-ID: <4F6C1201.9030300@samsung.com> (raw)
Hello, guys,
During our work we face to problem - get events about processes die in
user space (not all but some of them). In the past we had special module
which solve this problem.
But now I think that this task is quite native for cgroups subsystem.
Move interesting PIDs into special group and set event handler. We
investigate how events made in the memcg and implement proof of concepts
patch against mainline (maybe little bit old, but it's just RFC message)
with the same approach to "tasks" file.
So, I see several possible use cases for others with this patch.
1) replace wait4() for processes where we dont need for return status as
well as we want just know about changing status of some group of processes
2) As extension of 1, implementing some balancing mechanism in the user
space between several groups. For example if some process in one group
consume much system resources, processes in other groups will be
protected from slowdown.
3) Extremely useful in the libcgroup (in my mind), because now it's
unprotected against changing state with hands.
Need you opinion about this.
Thank you.
next reply other threads:[~2012-03-23 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 6:02 Nikiforov Alex [this message]
[not found] ` <4F6C1201.9030300-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-03-23 6:04 ` [RFC] event about group change Alexander Nikiforov
-- strict thread matches above, loose matches on Subject: below --
2012-04-02 4:19 Alexander Nikiforov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F6C1201.9030300@samsung.com \
--to=a.nikiforov-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=d.solodkiy-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.