[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b741c2440911021721o610ee4f1la123146e6e503d2d@mail.gmail.com>
Date: Tue, 3 Nov 2009 09:21:56 +0800
From: Liu Aleaxander <aleaxander@...il.com>
To: Li Zefan <lizf@...fujitsu.com>
Cc: Paul Menage <menage@...gle.com>, linux-kernel@...r.kernel.org,
"containers@...ts.osdl.org" <containers@...ts.osdl.org>
Subject: Re: [PATCH 2/3] Fix the 'current css_set' problem in debug subsystem
On Tue, Nov 3, 2009 at 9:05 AM, Li Zefan <lizf@...fujitsu.com> wrote:
> Liu Aleaxander wrote:
>>>>From 61c93b1a66e43d44820e9b8d22ef0bec80dfc814 Mon Sep 17 00:00:00 2001
>> From: Liu Aleaxander <Aleaxander@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists