From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: vatsa@linux.vnet.ibm.com, containers@lists.linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] CFS CGroup: Report usage
Date: Tue, 23 Oct 2007 13:27:40 +0530 [thread overview]
Message-ID: <471DA974.8060509@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830710230053l35fffaf5ld8882eaae8b9df7c@mail.gmail.com>
Paul Menage wrote:
> On 10/23/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>> Well, most people who care about deletion will use the notify_on_release
>> callback and retry.
>
> I'm not convinced this is true. Certainly the userspace approaches
> we're developing at Google don't (currently) use notify_on_release.
>
> Paul
Well, without notify_on_release you can never be sure if a new task
got added to the control group or if someone acquired a reference
to it. I can't think of a safe way of removing control groups/cpusets
without using notify_on_release.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-10-23 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 0:49 [PATCH 2/2] CFS CGroup: Report usage Paul Menage
2007-10-23 2:40 ` Srivatsa Vaddagiri
2007-10-23 6:06 ` Paul Menage
2007-10-23 7:21 ` Paul Menage
2007-10-23 7:49 ` Balbir Singh
2007-10-23 7:53 ` Paul Menage
2007-10-23 7:57 ` Balbir Singh [this message]
2007-10-23 8:08 ` Paul Menage
2007-10-23 16:41 ` Srivatsa Vaddagiri
2007-10-23 3:17 ` Balbir Singh
2007-10-23 6:09 ` Paul Menage
2007-10-23 16:43 ` Srivatsa Vaddagiri
2007-10-23 16:47 ` Srivatsa Vaddagiri
2007-10-23 16:41 ` Paul Menage
2007-10-23 17:38 ` Srivatsa Vaddagiri
2007-10-24 2:28 ` Paul Menage
2007-10-24 4:39 ` Srivatsa Vaddagiri
2007-10-26 1:24 ` Paul Menage
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=471DA974.8060509@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.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