From: "Paul Menage" <menage@google.com>
To: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
Cc: containers@lists.osdl.org, LKML <linux-kernel@vger.kernel.org>,
"Li Zefan" <lizf@cn.fujitsu.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] introduce task cgroup v2
Date: Wed, 11 Jun 2008 00:45:43 -0700 [thread overview]
Message-ID: <6599ad830806110045n6aec52ddkfb4be91b685357fe@mail.gmail.com> (raw)
In-Reply-To: <20080607195733.9C77.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Sat, Jun 7, 2008 at 4:00 AM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
> +
> +#include <linux/cgroup.h>
> +#include <linux/err.h>
> +#include <linux/cgroup_task.h>
> +
> +struct task_cgroup {
> + struct cgroup_subsys_state css;
> + /*
> + * the counter to account for number of thread.
> + */
> + int max_tasks;
> + int nr_tasks;
> +
> + spinlock_t lock;
> +};
This looks rather like a res_counter. Can you resuse that rather than
implementing your own read/write/charge/uncharge routines?
Paul
next prev parent reply other threads:[~2008-06-11 7:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 11:00 KOSAKI Motohiro
2008-06-10 5:22 ` Li Zefan
2008-06-16 2:16 ` KOSAKI Motohiro
2008-06-16 7:01 ` Li Zefan
2008-06-16 7:06 ` KOSAKI Motohiro
2008-06-11 7:45 ` Paul Menage [this message]
2008-06-16 1:32 ` KOSAKI Motohiro
2008-06-21 7:56 ` Paul Menage
2008-06-21 8:56 ` Balbir Singh
2008-06-21 9:10 ` KOSAKI Motohiro
2008-06-21 15:48 ` Paul Menage
2008-06-21 17:01 ` KOSAKI Motohiro
2008-06-21 17:04 ` Balbir Singh
2008-06-21 17:22 ` KOSAKI Motohiro
2008-06-14 4:46 ` Randy Dunlap
2008-06-16 2:07 ` KOSAKI Motohiro
2008-06-16 6:39 ` Peter Zijlstra
2008-06-16 6:59 ` KOSAKI Motohiro
2008-06-16 7:04 ` Peter Zijlstra
2008-06-16 7:07 ` Li Zefan
2008-06-16 7:09 ` KOSAKI Motohiro
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=6599ad830806110045n6aec52ddkfb4be91b685357fe@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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
all inboxes | Powered by JetHome®