From: "Kirill A. Shutemov" <kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
To: Alexander Nikiforov
<a.nikiforov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
KAMEZAWA Hiroyuki
<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
Glauber Costa <glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
Frederic Weisbecker
<fweisbec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [RFC] patch
Date: Mon, 2 Apr 2012 13:29:31 +0300 [thread overview]
Message-ID: <20120402102931.GA5885@shutemov.name> (raw)
In-Reply-To: <4F792976.4090503-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
On Mon, Apr 02, 2012 at 08:22:14AM +0400, Alexander Nikiforov wrote:
I think it should be part of task counter css, not core.
CC list updated.
> @@ -4558,6 +4594,22 @@ void cgroup_fork(struct task_struct *child)
> child->cgroups = current->cgroups;
> get_css_set(child->cgroups);
> INIT_LIST_HEAD(&child->cg_list);
> +
> + struct cgroupfs_root *root;
> +
> + /* send event to the userspace */
> + mutex_lock(&cgroup_mutex);
> + for_each_active_root(root) {
> + struct cgroup *cgrp;
> + struct fe_eventfd_list *ev;
> +
> + cgrp = task_cgroup_from_root(child, root);
> +
> + list_for_each_entry(ev, &cgrp->fe_notify, list) {
> + eventfd_signal(ev->eventfd, 1);
> + }
> + }
> + mutex_unlock(&cgroup_mutex);
> }
How does it affect performance?
>
> /**
> @@ -4653,6 +4705,7 @@ void cgroup_exit(struct task_struct *tsk, int run_callbacks)
> {
> struct css_set *cg;
> int i;
> + struct cgroupfs_root *root;
>
> /*
> * Unlink from the css_set task list if necessary.
> @@ -4666,6 +4719,20 @@ void cgroup_exit(struct task_struct *tsk, int run_callbacks)
> write_unlock(&css_set_lock);
> }
>
> + /* send event to the userspace */
> + mutex_lock(&cgroup_mutex);
> + for_each_active_root(root) {
> + struct cgroup *cgrp;
> + struct fe_eventfd_list *ev;
> +
> + cgrp = task_cgroup_from_root(tsk, root);
> +
> + list_for_each_entry(ev, &cgrp->fe_notify, list) {
> + eventfd_signal(ev->eventfd, 1);
> + }
> + }
> + mutex_unlock(&cgroup_mutex);
> +
I think it's racy. You need to notify userspace after reassigning the
task, not before.
> /* Reassign the task to the init_css_set. */
> task_lock(tsk);
> cg = tsk->cgroups;
--
Kirill A. Shutemov
next prev parent reply other threads:[~2012-04-02 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 4:19 [RFC] event about group change Alexander Nikiforov
[not found] ` <4F7928BE.8000502-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-04-02 4:22 ` [RFC] patch Alexander Nikiforov
[not found] ` <4F792976.4090503-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-04-02 10:29 ` Kirill A. Shutemov [this message]
[not found] ` <20120402102931.GA5885-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
2012-04-02 10:17 ` Alexander Nikiforov
2012-04-05 3:38 ` Alexander Nikiforov
[not found] ` <4F7D13AD.3030309-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-04-06 15:43 ` Frederic Weisbecker
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=20120402102931.GA5885@shutemov.name \
--to=kirill-okw7cidhh8elwutg50ltga@public.gmane.org \
--cc=a.nikiforov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fweisbec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox