From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH 1/8] PM: Add suspend block api. Date: Fri, 21 May 2010 08:35:39 +0200 Message-ID: <4BF629BB.9000805@kernel.org> References: <1272429119-12103-1-git-send-email-arve@android.com> <20100430172618.GA9043@redhat.com> <4BF4F31D.8070900@kernel.org> <201005210027.31910.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201005210027.31910.rjw@sisk.pl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: "Rafael J. Wysocki" Cc: Len Brown , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Jesse Barnes , Oleg Nesterov , Magnus Damm , linux-pm@lists.linux-foundation.org, Wu Fengguang , Andrew Morton List-Id: linux-pm@vger.kernel.org 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