public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@crca.org.au>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Pavel Machek <pavel@ucw.cz>,
	pm list <linux-pm@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	TuxOnIce-devel <tuxonice-devel@tuxonice.net>
Subject: Re: [TuxOnIce-devel] [SUSPECTED SPAM] Re: [linux-pm] Proposal for a new algorithm for reading & writing a hibernation image.
Date: Sun, 06 Jun 2010 09:01:40 +1000	[thread overview]
Message-ID: <4C0AD754.7060800@crca.org.au> (raw)
In-Reply-To: <88D03BC9-5E85-482D-9431-F1CE4C958C9B@mit.edu>

Hi.

On 05/06/10 22:59, Theodore Tso wrote:
>
> On Jun 4, 2010, at 8:05 PM, Nigel Cunningham wrote:
>>> 2mb pages will probably present a problem, as will bat mappings on powerpc.
>>
>> I have the idea that 2MB pages are only used for the kernel text and read only data. Is that right? If so, perhaps they can just be unconditionally copied (so that we can restore the image if a different kernel is booted) and wouldn't need any page protection. Does that sound right?
>
> No, hugepages are available for use by userspace programs.
>
> See: https://lwn.net/Articles/374424/

Ta!

I'll take a look.

Nigel

  reply	other threads:[~2010-06-05 23:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 14:50 [SUSPECTED SPAM] Re: [linux-pm] Proposal for a new algorithm for reading & writing a hibernation image Pavel Machek
2010-06-04 23:39 ` Maxim Levitsky
2010-06-04 23:58   ` Nigel Cunningham
2010-06-05  0:36     ` Maxim Levitsky
2010-06-05  0:45       ` Maxim Levitsky
2010-06-05  3:37         ` Nigel Cunningham
2010-06-05  0:47       ` Nigel Cunningham
2010-06-05  1:16         ` Maxim Levitsky
2010-06-05  3:17           ` Nigel Cunningham
2010-06-05  0:05 ` Nigel Cunningham
2010-06-05 12:59   ` [TuxOnIce-devel] " Theodore Tso
2010-06-05 23:01     ` Nigel Cunningham [this message]
2010-06-05  0:20 ` [linux-pm] [SUSPECTED SPAM] " Nigel Cunningham
2010-06-05 18:45   ` Rafael J. Wysocki
2010-06-05 19:10     ` Maxim Levitsky
2010-06-05 19:21       ` Rafael J. Wysocki
2010-06-05 22:54         ` Nigel Cunningham
2010-06-05 23:20           ` Rafael J. Wysocki
2010-06-06  7:01             ` Nigel Cunningham
2010-06-06 14:06               ` Rafael J. Wysocki
2010-06-07  5:23                 ` Nigel Cunningham
2010-06-07  8:40                   ` Rafael J. Wysocki
2010-06-06  0:40         ` Maxim Levitsky
2010-06-06 13:57           ` Rafael J. Wysocki
2010-06-06 15:54             ` Maxim Levitsky
2010-06-06 19:04               ` Rafael J. Wysocki
2010-06-06 19:51                 ` Maxim Levitsky
2010-06-06 21:55                 ` Pedro Ribeiro
2010-06-07  8:41                   ` Rafael J. Wysocki
2010-06-07  5:31                 ` Nigel Cunningham
2010-06-07  8:49                   ` Rafael J. Wysocki
2010-06-08  2:07                     ` Nigel Cunningham
2010-06-08  9:01                       ` Rafael J. Wysocki
2010-06-07 13:07                   ` [TuxOnIce-devel] " Martin Steigerwald
2010-06-07 21:28                     ` Rafael J. Wysocki
2010-06-07 21:31                       ` Nigel Cunningham
2010-06-07  5:28             ` Nigel Cunningham

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=4C0AD754.7060800@crca.org.au \
    --to=ncunningham@crca.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=tuxonice-devel@tuxonice.net \
    --cc=tytso@MIT.EDU \
    /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