From: Liu Aleaxander <aleaxander@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Paul Menage <menage@google.com>,
linux-kernel@vger.kernel.org,
"containers@lists.osdl.org" <containers@lists.osdl.org>
Subject: Re: [PATCH 2/3] Fix the 'current css_set' problem in debug subsystem
Date: Tue, 3 Nov 2009 09:21:56 +0800 [thread overview]
Message-ID: <b741c2440911021721o610ee4f1la123146e6e503d2d@mail.gmail.com> (raw)
In-Reply-To: <4AEF81E2.3060403@cn.fujitsu.com>
On Tue, Nov 3, 2009 at 9:05 AM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> Liu Aleaxander wrote:
>>>From 61c93b1a66e43d44820e9b8d22ef0bec80dfc814 Mon Sep 17 00:00:00 2001
>> From: Liu Aleaxander <Aleaxander@gmail.com>
>> Date: Mon, 2 Nov 2009 14:30:07 +0800
>> Subject: [PATCH 2/3] Fix the 'current css_set' problem in debug subsystem
>>
>> In the current implementation, it always print the same information
>> no matter which group you are in. And this would be meaningless. So
>> we should make it print the information of the 'real' current one.
>>
>> Well, I am not sure it's the current one, but I'm sure it's the first
>> one of that cgroup.
>>
>
> I don't think there is a bug with current 'curent_css_set'. The
> "current" in all debug.current_xxx interfaces means "current task".
Yes, I know it means 'current task', but is this useful to print the
same things with two more files in all the cgroups?
> Besides we already print out a cgroup's css links through
> debug.cgroup_css_links, without showing the refcount of
> each css_set, but we can, if it can be useful:
>
> # cat debug.cgroup_css_links
> css_set c10d92e0
Good link:)
--
regards
Liu Aleaxander
next prev parent reply other threads:[~2009-11-03 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 7:46 Liu Aleaxander
2009-11-03 1:05 ` Li Zefan
2009-11-03 1:21 ` Liu Aleaxander [this message]
2009-11-03 1:23 ` 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=b741c2440911021721o610ee4f1la123146e6e503d2d@mail.gmail.com \
--to=aleaxander@gmail.com \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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®