public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm <linux-pm@lists.linux-foundation.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Len Brown <lenb@kernel.org>,
	"Barnes, Jesse" <jesse.barnes@intel.com>
Subject: Re: [RFC PATCH 0/3] pm: device parallel resume mechanism
Date: Mon, 22 Dec 2008 21:19:32 +0100	[thread overview]
Message-ID: <200812222119.32833.rjw@sisk.pl> (raw)
In-Reply-To: <1229915522.562.164.camel@rzhang-dt>

On Monday, 22 of December 2008, Zhang Rui wrote:
> Hi, rafael 

Hi,

> On Sat, 2008-12-20 at 01:15 +0800, Rafael J. Wysocki wrote:
> > On Friday, 19 of December 2008, Zhang Rui wrote:
> > > Hi, all,
> > > 
> > > The resume process can be split into 3 parts, BIOS resume time, kernel
> > > resume time and X/application resume time.
> > > And device resume takes most of the kernel resume time.
> > > this patch set introduces a new mechanism to resume device in parallel
> > > which can reduce the device resume time a lot.
> > > 
> > > In this proposal, some devices can create its own workqueue for
> > > parallel resume. And for all the other devices that depends on this
> > > device, their resume methods are queued in the same workqueue.
> > > And we flush all the workqueues before resuming X/applications.
> > > 
> > > As the devices vary from different platforms. it's hard to give an exact
> > > number of how much time it can reduce.
> > > Here are some of my test results:
> > > 1. eeepc901, kernel resume time can be reduced from about 2.1 seconds to
> > > 1.6 seconds.
> > > 2. a SantaRosa testbox, kernel resume time can be reduced from about
> > > 3.5s to 2s.
> > > 
> > > please review this patch. Any comments are welcome. :)
> > 
> > Well, given that our single-thread resume is not exactly correct,
> you mean that the current serial resume mechanism still doesn't work
> stable, right?

Not exactly.  I mean it isn't _done_ right and not working correctly is just a
consequence of this.

For this reason, we should first fix the current code and _then_ build add new
features like this, not the other way around.

> 
> >  I think it's _way_ to early to indroduce things like this.
> Right, it's not for upstream.
> But it looks good in theory, and it does works without any side effect
> in my case.
> So the patch was sent out here to see if there are some problems that
> are not covered by this patch, like the one Alan pointed out. :)

OK

Thanks,
Rafael

      reply	other threads:[~2008-12-22 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  6:34 [RFC PATCH 0/3] pm: device parallel resume mechanism Zhang Rui
2008-12-19 17:15 ` Rafael J. Wysocki
2008-12-22  3:12   ` Zhang Rui
2008-12-22 20:19     ` Rafael J. Wysocki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200812222119.32833.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jesse.barnes@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rui.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox