[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4811C978.6010508@fr.ibm.com>
Date: Fri, 25 Apr 2008 14:07:20 +0200
From: Cedric Le Goater <clg@...ibm.com>
To: Pavel Machek <pavel@....cz>
CC: Matt Helsley <matthltc@...ibm.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux-Kernel <linux-kernel@...r.kernel.org>,
Paul Menage <menage@...gle.com>,
Oren Laadan <orenl@...columbia.edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-pm@...ts.linux-foundation.org,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [RFC][PATCH 2/5] Container Freezer: Make refrigerator always
available
Pavel Machek wrote:
> Hi!
>
>> Now that the TIF_FREEZE flag is available in all architectures,
>> extract the refrigerator() and freeze_task() from kernel/power/process.c
>> and make it available to all.
>>
>> The refrigerator() can now be used in a control group subsystem
>> implementing a control group freezer.
>>
>> Signed-off-by: Cedric Le Goater <clg@...ibm.com>
>> Signed-off-by: Matt Helsley <matthltc@...ibm.com>
>> Tested-by: Matt Helsley <matthltc@...ibm.com>
>
> There's no problem with doing this... but you should get some debate
> (with Linus?) whether using freezer for cgroups is sane.
Yes that's what we are trying to know, is the fake signal mechanism
used by the freezer something we can build upon ?
> When that is done, there's no problem with this going in, probably
> through rafael's patch queue.
OK
> (The first patch -- add freezer for all archs -- is probably
> reasonably to go in ASAP, through akpm or something...)
Thanks,
C.
--
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