linux-kernel - Re: [RFC PATCH v2] suspend/resume performance improvement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8603263.ZsHYMQGz6a@vostro.rjw.lan>
Date:	Mon, 01 Jun 2015 11:51:20 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	eun.taik.lee@...sung.com
Cc:	"pavel@....cz" <pavel@....cz>,
	"len.brown@...el.com" <len.brown@...el.com>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2] suspend/resume performance improvement

On Sunday, May 31, 2015 05:07:42 AM EunTaik Lee wrote:
> 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)

How long?  Perhaps this is not the only explanation of the delay?

> 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.
> 
> Signed-off-by: Eun Taik Lee <eun.taik.lee@...sung.com>

First, if you send a v2, please say what's changed since v1.

Second, this most likely is hiding a problem of some sort and the theory
about the time slice being used up entirely by the suspend process is not
convincing.

Also the patch duplicates exsiting functionality that should be extended
instead if anything.


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/