From: EunTaik Lee <eun.taik.lee@samsung.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "pavel@ucw.cz" <pavel@ucw.cz>,
"len.brown@intel.com" <len.brown@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [RFC PATCH] suspend/resume performance improvement
Date: Wed, 27 May 2015 01:32:34 +0000 (GMT) [thread overview]
Message-ID: <310063525.576351432690353260.JavaMail.weblogic@epmlwas01d> (raw)
>> When a task that calls state_store() to suspend
>> the device has used up most of its time slice,
>> suspend sometimes take too long. (User noticeable)
>>
>> Suspend/resume is a system wide operation.
>> So, instead of depending on a userspace task's time
>> slice, let kworker do the work to avoid a long wait
>> on the runqueue.
> All of that seems to duplicate the existing autosleep.c functionality.
Yes, the effect of using the kworker in autosleep will be same performance-wise.
But if a platform doesn't use the autosleep functionality then we still have the problem.
So doesn't it make sense to implement it for the autosleep-disabled use cases?
next reply other threads:[~2015-05-27 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 1:32 EunTaik Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 1:41 Re: [RFC PATCH] suspend/resume performance improvement EunTaik Lee
2015-05-27 10:38 EunTaik Lee
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=310063525.576351432690353260.JavaMail.weblogic@epmlwas01d \
--to=eun.taik.lee@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).