linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Nigel Cunningham <ncunningham@crca.org.au>,
	Matt Tolentino <matthew.e.tolentino@intel.com>,
	linux-pm@lists.osdl.org, Dave Hansen <haveblue@us.ibm.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, pavel@suse.cz,
	Mel Gorman <mel@skynet.ie>, Andy Whitcroft <apw@shadowen.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-pm] [PATCH] hibernation should work ok with memory hotplug
Date: Tue, 4 Nov 2008 09:54:33 +0100	[thread overview]
Message-ID: <200811040954.34969.rjw@sisk.pl> (raw)
In-Reply-To: <1225784174.12673.547.camel@nimitz>

On Tuesday, 4 of November 2008, Dave Hansen wrote:
> On Tue, 2008-11-04 at 08:08 +0100, Rafael J. Wysocki wrote:
> > A pfn always refers to specific page frame and/or struct page, so yes.
> > However, in one of the nodes these pfns are sort of "invalid" (they point
> > to struct pages belonging to other zones).  AFAICS.
> 
> Part of this problem is getting out of the old zone mindset.  It used to
> be that there were one, two, or three zones, set up at boot, with static
> ranges.  These never had holes, never changed, and were always stacked
> up nice and tightly on top of one another.  It ain't that way no more.

In fact there were two assumptions about zones in the hibernation code,
that they are static and that they don't overlap.  The second one may be
removed by the patch I sent before, but there still is a problem related to
the first one, which is that the memory management structures (bitmaps) used
by us depend on the zones being static.

Of course, we create the image atomically, but the bitmaps are created earlier
with the assumption that the zones won't change aferwards.  Also, if memory
hotplugging is used _after_ the image has been created, the zones may change
in a way that's not compatible with the structure of the bitmaps.

To handle this, I need to know two things:
1) what changes of the zones are possible due to memory hotplugging (i.e.
   can they grow, shring, change boundaries etc.)
2) what kind of locking is needed to prevent zones from changing.

Thanks,
Rafael

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-11-04  8:54 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081029105956.GA16347@atrey.karlin.mff.cuni.cz>
     [not found] ` <200810291325.01481.rjw@sisk.pl>
2008-11-03 20:51   ` Andrew Morton
2008-11-03 21:18     ` [linux-pm] " Nigel Cunningham
2008-11-03 21:21     ` Dave Hansen
2008-11-03 22:24       ` Rafael J. Wysocki
2008-11-03 22:34         ` Dave Hansen
2008-11-03 23:05           ` Rafael J. Wysocki
2008-11-03 23:10             ` Dave Hansen
2008-11-04  0:29               ` Rafael J. Wysocki
2008-11-04  0:52                 ` Dave Hansen
2008-11-03 23:39           ` Andy Whitcroft
2008-11-04  4:02           ` [linux-pm] " Nigel Cunningham
2008-11-04  7:08             ` Rafael J. Wysocki
2008-11-04  7:36               ` Dave Hansen
2008-11-04  8:54                 ` Rafael J. Wysocki [this message]
2008-11-04 15:21                   ` Dave Hansen
2008-11-04 15:35                     ` Rafael J. Wysocki
2008-11-04 15:39                       ` Dave Hansen
2008-11-04 16:34                         ` Rafael J. Wysocki
2008-11-04 16:59                           ` Dave Hansen
2008-11-05  0:38                             ` KAMEZAWA Hiroyuki
2008-11-05 11:08                               ` Rafael J. Wysocki
2008-11-06  0:14                                 ` KAMEZAWA Hiroyuki
2008-11-06  0:28                                   ` Dave Hansen
2008-11-06  0:53                                     ` KAMEZAWA Hiroyuki
2008-11-06  2:03                                       ` Nigel Cunningham
2008-11-06  2:13                                         ` KAMEZAWA Hiroyuki
2008-11-06 14:47                                       ` Alan Stern
2008-11-07  1:09                                         ` KAMEZAWA Hiroyuki
2008-11-06  8:47                                     ` Pavel Machek
2008-11-06  1:17                                   ` KAMEZAWA Hiroyuki
2008-11-06  1:43                                     ` Nigel Cunningham
2008-11-06  1:54                                       ` KAMEZAWA Hiroyuki
2008-11-06  1:59                                         ` KAMEZAWA Hiroyuki
2008-11-06  2:00                                         ` Nigel Cunningham
2008-11-06  2:07                                           ` KAMEZAWA Hiroyuki
2008-11-06  3:12                                             ` KAMEZAWA Hiroyuki
2008-11-06  3:28                                               ` Yasunori Goto
2008-11-06  6:04                                                 ` KAMEZAWA Hiroyuki
2008-11-06 14:48                                           ` Alan Stern
2008-11-06 20:46                                             ` Nigel Cunningham
2008-11-06  9:12                                     ` Pavel Machek
2008-11-06  9:12                                       ` KAMEZAWA Hiroyuki
2008-11-06  9:26                                         ` Nigel Cunningham
2008-11-06 14:43                                   ` Alan Stern
2008-11-04  7:09             ` Dave Hansen
2008-11-04  7:30               ` Nigel Cunningham
2008-11-04  7:53                 ` Dave Hansen
2008-11-05  9:10                   ` Nigel Cunningham
2008-11-05 10:58                     ` Rafael J. Wysocki
2008-11-05 16:23                     ` Dave Hansen
2008-11-06 12:28     ` Pavel Machek

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=200811040954.34969.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=mel@skynet.ie \
    --cc=ncunningham@crca.org.au \
    --cc=pavel@suse.cz \
    /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