From: "Huang, Ying" <ying.huang@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: nigel@nigel.suspend2.net,
Kexec Mailing List <kexec@lists.infradead.org>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pm@lists.linux-foundation.org,
Jeremy Maitin-Shepard <jbms@cmu.edu>
Subject: Re: [PATCH 0/2 -mm] kexec based hibernation -v5
Date: Fri, 12 Oct 2007 11:19:32 +0800 [thread overview]
Message-ID: <1192159172.17539.26.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <200710111217.58473.rjw@sisk.pl>
On Thu, 2007-10-11 at 12:17 +0200, Rafael J. Wysocki wrote:
> On Thursday, 11 October 2007 04:13, Huang, Ying wrote:
> > Kexec base hibernation has some potential advantages over uswsusp and
> > TuxOnIce (suspend2). Some most obvious advantages are:
>
> Well, I have some doubts as far as the obviousness is concerned.
OK, I will remove the "obvious".
> > 1. The hibernation image size can exceed half of memory size easily.
>
> This is also possible with TuxOnIce.
I will add detail description about this. It is possible with TuxOnIce,
and hard with u/swsusp.
>
> > 2. The hibernation image can be written to and read from almost
> > anywhere, such as USB disk, NFS.
>
> This is possible with uswsusp, at least in theory, probably with TuxOnIce too.
I will remove this.
> > 3. It is possible to eliminate freezer from kexec based hibernation
> > implementation.
>
> This isn't true as long as we have not changed the handling of devices
> (which is in the works, but will take time).
I know it has not been implemented yet. I just say that it is possible
for khibernation and it is almost impossible for u/swsusp and TuxOnIce.
> > 4. Based on kexec/kdump implementation, the kernel code needed is
> > less.
>
> Well, maybe.
>
Best Regards,
Huang Ying
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: "Huang, Ying" <ying.huang@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Machek <pavel@ucw.cz>,
nigel@nigel.suspend2.net,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Maitin-Shepard <jbms@cmu.edu>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH 0/2 -mm] kexec based hibernation -v5
Date: Fri, 12 Oct 2007 11:19:32 +0800 [thread overview]
Message-ID: <1192159172.17539.26.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <200710111217.58473.rjw@sisk.pl>
On Thu, 2007-10-11 at 12:17 +0200, Rafael J. Wysocki wrote:
> On Thursday, 11 October 2007 04:13, Huang, Ying wrote:
> > Kexec base hibernation has some potential advantages over uswsusp and
> > TuxOnIce (suspend2). Some most obvious advantages are:
>
> Well, I have some doubts as far as the obviousness is concerned.
OK, I will remove the "obvious".
> > 1. The hibernation image size can exceed half of memory size easily.
>
> This is also possible with TuxOnIce.
I will add detail description about this. It is possible with TuxOnIce,
and hard with u/swsusp.
>
> > 2. The hibernation image can be written to and read from almost
> > anywhere, such as USB disk, NFS.
>
> This is possible with uswsusp, at least in theory, probably with TuxOnIce too.
I will remove this.
> > 3. It is possible to eliminate freezer from kexec based hibernation
> > implementation.
>
> This isn't true as long as we have not changed the handling of devices
> (which is in the works, but will take time).
I know it has not been implemented yet. I just say that it is possible
for khibernation and it is almost impossible for u/swsusp and TuxOnIce.
> > 4. Based on kexec/kdump implementation, the kernel code needed is
> > less.
>
> Well, maybe.
>
Best Regards,
Huang Ying
next prev parent reply other threads:[~2007-10-12 3:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 2:13 [PATCH 0/2 -mm] kexec based hibernation -v5 Huang, Ying
2007-10-11 2:13 ` Huang, Ying
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-11 10:17 ` Rafael J. Wysocki
2007-10-12 3:19 ` Huang, Ying [this message]
2007-10-12 3:19 ` Huang, Ying
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-12 11:37 ` Rafael J. Wysocki
2007-10-12 3:19 ` Huang, Ying
2007-10-19 19:53 ` Phillip Susi
2007-10-19 19:53 ` Phillip Susi
2007-10-19 19:53 ` Phillip Susi
2007-10-20 1:53 ` david
2007-10-20 1:53 ` david
2007-10-20 1:53 ` david
2007-10-20 5:50 ` huang ying
2007-10-20 5:50 ` huang ying
2007-10-20 5:50 ` huang ying
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 2:13 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=1192159172.17539.26.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--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@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.