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]
Date:	Wed, 29 Aug 2007 12:41:25 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	"Huang, Ying" <ying.huang@...el.com>
CC:	"Hu, Fenghua" <fenghua.hu@...el.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Pavel Machek <pavel@....cz>, nigel@...el.suspend2.net,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jeremy Maitin-Shepard <jbms@....edu>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-pm@...ts.linux-foundation.org,
	Kexec Mailing List <kexec@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] [RFC][PATCH 0/2 -mm] kexec based hibernation

Huang, Ying wrote:
> On Mon, 2007-08-27 at 09:28 +0800, Hu, Fenghua wrote:
> 
>>One quick question is, can it improve hiberation/wakeup time?
> 
> 
> In general, for kexec based hibernation, what increases
> hibernation/wakeup time:
> 
> - One extra Linux boot is needed to hibernate and wakeup.
> 
> 
> What decreases hibernation/wakeup time:
> 
> - Most hibernation/wakeup work is done in full functional user space
> program, so it is possible to do some optimization, such as parallel
> compression.

- It does not have to reclaim pagecache before suspend?

- It does not have to restore working set afterwards?

(You could do this to reduce image size, of course, but it can
be optional which is nice).


> So, I think the kexec based hibernation may be slower than original
> implementation in general. In this prototype implementation, the
> hibernation/wakeup time is much longer than original hibernation/wakeup
> implementation. But it has much to be optimized and I think it can
> approach the speed of the original implementation after optimization.

Also, don't just look at the time to do a simple suspend/resume cycle,
but the full cost of going from working state to working state (eg.
grep a kernel tree or two!).

Although the kexec details are out of my league, I really like
everything about the concept :) Nice work.

-- 
SUSE Labs, Novell Inc.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ