linux-kernel - Re: [PATCH -mm] Allow selective freezing of the system for different events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070428074533.GA15607@in.ibm.com>
Date:	Sat, 28 Apr 2007 13:15:33 +0530
From:	Gautham R Shenoy <ego@...ibm.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, Ingo Molnar <mingo@...e.hu>,
	Oleg Nesterov <oleg@...sign.ru>, Pavel Machek <pavel@....cz>,
	Pekka Enberg <penberg@...helsinki.fi>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -mm] Allow selective freezing of the system for different events

On Fri, Apr 27, 2007 at 11:22:22PM -0700, Andrew Morton wrote:
> On Sat, 28 Apr 2007 07:04:46 +0530 Gautham R Shenoy <ego@...ibm.com> wrote:
> 
> > This patch
> > * Provides an interface to selectively freeze the system for different events.
> > * Allows tasks to exempt themselves or other tasks from specific freeze
> >   events.
> > * Allow nesting of freezer calls. For eg:
> > 
> > 	freeze_processes(EVENT_A);
> > 	/* Do something with respect to event A */
> > 	.
> > 	.
> > 	.
> > 	freeze_processes(EVENT_B);
> > 	/* Do something with respect to event B */
> > 	.
> > 	.
> > 	.
> > 	thaw_processes(EVENT_B);
> > 	.
> > 	.
> > 	.
> > 	thaw_processes(EVENT_B);
> > 
> > This type of behaviour would be required when cpu hotplug would start
> > using the process freezer, where EVENT_A would be SUSPEND and EVENT_B
> > would be HOTPLUG_CPU.
> > 
> > This patch applies on the top of 2.6.21-rc7-mm2 + Rafael's freezer
> > changes from http://lkml.org/lkml/2007/4/27/302.
> 
> I think I'll duck this.  We have more than enough kthread/freezer/etc work
> queued for 2.6.22. 

Sure, not a problem :-)

I just wanted to get a sense, if this was a right way to do it. 
Besides, I am plannning to send it again once I port the cpuhotplug
patches on top of all these changes and get some satisfactory numbers.

> Let's please for now concentrate on reviewing and
> testing the existing changes.  Once that has all landed and settled in,
> let's start thinking about the next round.
> 

Ok.

Thanks and Regards
gautham.
-- 
Gautham R Shenoy
Linux Technology Center
IBM India.
"Freedom comes with a price tag of responsibility, which is still a bargain,
because Freedom is priceless!"
-
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/