Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753872AbaBQBof (ORCPT ); Sun, 16 Feb 2014 20:44:35 -0500 Received: from mga11.intel.com ([192.55.52.93]:35869 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753869AbaBQBod (ORCPT ); Sun, 16 Feb 2014 20:44:33 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.95,857,1384329600"; d="scan'208";a="476277940" From: "Liu, Chuansheng" To: "Rafael J. Wysocki" CC: "gregkh@linuxfoundation.org" , "pavel@ucw.cz" , "Brown, Len" , "linux-pm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Li, Zhuangzhi" Subject: RE: [PATCH 0/5] Enabling the asynchronous threads for other phases Thread-Topic: [PATCH 0/5] Enabling the asynchronous threads for other phases Thread-Index: AQHPK26CZz6OAwG6HkWM9bZGnTNqJJq4qvoA Date: Mon, 17 Feb 2014 01:44:28 +0000 Message-ID: <27240C0AC20F114CBF8149A2696CBE4A01C21FC2@SHSMSX101.ccr.corp.intel.com> References: <1390207479-26064-1-git-send-email-chuansheng.liu@intel.com> <2360514.bLFmJYMItS@vostro.rjw.lan> <27240C0AC20F114CBF8149A2696CBE4A01C1AF9E@SHSMSX101.ccr.corp.intel.com> <9364493.5ysfSuJl7g@vostro.rjw.lan> In-Reply-To: <9364493.5ysfSuJl7g@vostro.rjw.lan> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id s1H1idjV014007 Hello Rafael, > -----Original Message----- > From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net] > Sent: Monday, February 17, 2014 7:41 AM > To: Liu, Chuansheng > Cc: gregkh@linuxfoundation.org; pavel@ucw.cz; Brown, Len; > linux-pm@vger.kernel.org; linux-kernel@vger.kernel.org; Li, Zhuangzhi > Subject: Re: [PATCH 0/5] Enabling the asynchronous threads for other phases > > On Monday, February 10, 2014 08:36:57 AM Liu, Chuansheng wrote: > > Hello Rafael, > > > > > -----Original Message----- > > > From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net] > > > Sent: Thursday, February 06, 2014 5:53 AM > > > To: Liu, Chuansheng > > > Cc: gregkh@linuxfoundation.org; pavel@ucw.cz; Brown, Len; > > > linux-pm@vger.kernel.org; linux-kernel@vger.kernel.org; Li, Zhuangzhi > > > Subject: Re: [PATCH 0/5] Enabling the asynchronous threads for other > phases > > > > > > On Monday, January 20, 2014 04:44:34 PM Liu, Chuansheng wrote: > > > > Hello, > > > > > > > > This patch series are for enabling the asynchronous threads for the > phases > > > > resume_noirq, resume_early, suspend_noirq and suspend_late. > > > > > > > > Just like commit 5af84b82701a and 97df8c12995, with async threads it > will > > > > reduce the system suspending and resuming time significantly. > > > > > > > > With these patches, in my test platform, it saved 80% time in > resume_noirq > > > > phase. > > > > > > > > Has done the suspend-resume stress test for a long time, please help to > > > > review. > > > > > > > > Best Regards, > > > > > > > > [PATCH 1/5] PM: Adding two flags for async suspend_noirq and > > > > [PATCH 2/5] PM: Enabling the asynchronous threads for resume_noirq > > > > [PATCH 3/5] PM: Enabling the asyncronous threads for resume_early > > > > [PATCH 4/5] PM: Enabling the asyncronous threads for suspend_noirq > > > > [PATCH 5/5] PM: Enabling the asyncronous threads for suspend_late > > > > > > I've applied this to the bleeding-edge branch of the linux-pm.git tree, with > > > minor changes related to coding style, white space etc. > > Thanks your help. > > Unfortunately, I've just realized that your patches don't add any mechanism > ensuring that parent devices' .suspend_noirq() will be called *after* the > .suspend_noirq() of all their children. Of course, analogously for > .suspend_late() and for the resume part (where children have to wait for > their parents). > > In the original async suspend/resume code that is implemented using > power.completion and I suppose you can do the same thing here. I think "parent devices suspend after their children" is not related directly with using async or not; In the original code, even without asyncing, the suspend/resume has the waiting action, but there no waiting action for suspend_noirq and other phases. If you think the parent waiting for children is necessary for suspend_noirq/suspend_late /resume_early/resume_noirq, I can cook other series patches. But we can separate them with current asyncing series patches. Agree? ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?