[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4BF629BB.9000805@kernel.org>
Date: Fri, 21 May 2010 08:35:39 +0200
From: Tejun Heo <tj@...nel.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
CC: Oleg Nesterov <oleg@...hat.com>,
Arve Hjønnevåg <arve@...roid.com>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Randy Dunlap <rdunlap@...otime.net>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Magnus Damm <damm@...l.co.jp>,
Nigel Cunningham <nigel@...onice.net>,
Cornelia Huck <cornelia.huck@...ibm.com>,
Ming Lei <tom.leiming@...il.com>,
Wu Fengguang <fengguang.wu@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Maxim Levitsky <maximlevitsky@...il.com>,
linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/8] PM: Add suspend block api.
Hello,
On 05/21/2010 12:27 AM, Rafael J. Wysocki wrote:
>> Oh, this isn't an issue w/ cmwq. While frozen all new works are
>> collected into per-cpu delayed worklist and while frozen trustee in
>> charge of the cpu will keep waiting. Once thawed, trustee will
>> execute all works including the delayed ones unbound to any cpu.
>
> So, does it require any intrusive changes to make it possible to create
> multithread freezable workqueues?
cmwq itself is quite intrusive changes but w/ cmwq it just takes
flipping a flag when creating the queue.
Thanks.
--
tejun
--
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