From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: "\"Paul (??) Menage\"" <menage@google.com>
Cc: dhaval@linux.vnet.ibm.com, Pavel Emelianov <xemul@sw.ru>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Paul Jackson <pj@sgi.com>,
Linux Containers <containers@lists.osdl.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Containers: css_put() dilemma
Date: Tue, 17 Jul 2007 23:41:55 +0530 [thread overview]
Message-ID: <469D066B.6050606@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830707171044u38c0a940r12d2bc80b475ead4@mail.gmail.com>
Paul (??) Menage wrote:
> On 7/17/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>>
>> That sounds correct. I wonder now if the solution should be some form
>> of delegation for deletion of unreferenced containers (HINT: work queue
>> or kernel threads).
>
> What a great idea. In fact, that's exactly what the release agent
> patch already does.
:-) I should have seen that. I am a little lost thinking that
container_rmdir() and the release agent check_for_release() work
without too much knowledge of each other. BTW, what are the semantics
of css_put() is it expected to free the container/run the release agent
when the reference count of the container_subsys_state drops to zero?
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-07-17 18:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 18:50 Containers: css_put() dilemma Balbir Singh
2007-07-16 19:03 ` Paul (宝瑠) Menage
2007-07-17 2:21 ` Balbir Singh
2007-07-17 2:35 ` Paul (宝瑠) Menage
2007-07-17 7:00 ` Balbir Singh
2007-07-17 7:18 ` Paul (宝瑠) Menage
2007-07-17 10:28 ` Balbir Singh
2007-07-17 15:49 ` Paul (宝瑠) Menage
2007-07-17 16:02 ` Dave Hansen
2007-07-17 16:15 ` Paul (宝瑠) Menage
2007-07-17 17:23 ` Paul Jackson
2007-07-17 17:40 ` Balbir Singh
2007-07-17 17:44 ` Paul (宝瑠) Menage
2007-07-17 17:55 ` Paul Jackson
2007-07-17 17:57 ` Paul (宝瑠) Menage
2007-07-17 18:11 ` Balbir Singh [this message]
2007-07-17 18:26 ` Paul (宝瑠) Menage
2007-07-18 4:29 ` Balbir Singh
2007-07-18 5:30 ` Balbir Singh
2007-07-18 5:52 ` Srivatsa Vaddagiri
2007-07-18 23:15 ` Paul Menage
2007-07-19 3:44 ` Balbir Singh
2007-07-18 6:07 ` Paul (宝瑠) Menage
2007-07-17 17:53 ` Paul Jackson
2007-07-17 17:55 ` Paul (宝瑠) Menage
2007-07-17 17:58 ` Paul Jackson
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=469D066B.6050606@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=xemul@sw.ru \
/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