public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Jeremy Maitin-Shepard <jbms@cmu.edu>,
	Alan Stern <stern@rowland.harvard.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	david@lang.hm, linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org,
	Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation
Date: Sun, 15 Jul 2007 19:08:04 +1000	[thread overview]
Message-ID: <200707151908.05388.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <1184483593.1898.98.camel@caritas-dev.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

Hi.

On Sunday 15 July 2007 17:13:13 Huang, Ying wrote:
> The complete changelog of the patch is as follow:
> 
> ---
> 
> Kexec base hibernation has some potential advantages over uswsusp and
> TuxOnIce (suspend2). Some most obvious advantages are:
> 
> 1. The hibernation image size can exceed half of memory size easily.
> 2. The hibernation image can be written to and read from almost
>    anywhere, such as USB disk, NFS.

This isn't right. TuxOnIce has no problem with image sizes exceeding half the 
amount of memory, and both uswsusp and TuxOnIce could write to a USB disk/key 
or NFS as well. Historically, the issue with writing to USB devices has been 
an issue with USB device drivers, not hibernation implementations. I haven't 
tried writing an image to USB, but with the work on the drivers, I wouldn't 
be surprised if it was usable now. NFS? Again, I haven't tried, but wouldn't 
expect it to be impossible. I did try writing an image to an NBD device a 
couple of years ago. It didn't quite work, but wasn't far away.
 
Regards,

Nigel
-- 
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-15 22:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15  7:13 [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation Huang, Ying
2007-07-15  9:08 ` Nigel Cunningham [this message]
2007-07-15 10:09 ` Rafael J. Wysocki
2007-07-19  1:04 ` Andrew Morton
2007-07-19  2:15   ` Nigel Cunningham
2007-07-19  3:30     ` david
2007-07-19  6:43   ` Huang, Ying
2007-07-19  9:13     ` Rafael J. Wysocki
2007-07-31  9:10 ` Pavel Machek
2007-07-31  9:25   ` Huang, Ying
2007-07-31 10:52     ` Eric W. Biederman
2007-07-31 11:12       ` Pavel Machek
2007-08-01  1:16       ` Huang, Ying
2007-07-31 11:14     ` Pavel Machek
2007-07-31 11:04 ` Pavel Machek
2007-08-01  1:34   ` Huang, Ying
2007-08-05 18:55     ` Pavel Machek
2007-08-06  2:31       ` Huang, Ying
2007-08-06  9:02         ` Pavel Machek
2007-08-06 13:22           ` Huang, Ying

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=200707151908.05388.nigel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=akpm@linux-foundation.org \
    --cc=david@lang.hm \
    --cc=ebiederm@xmission.com \
    --cc=jbms@cmu.edu \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nigel@suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=ying.huang@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