public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Nigel Cunningham <nigel@suspend2.net>,
	Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC][PATCH] swsusp: support creating bigger images
Date: Wed, 26 Apr 2006 23:16:43 +0200	[thread overview]
Message-ID: <200604262316.44162.rjw@sisk.pl> (raw)
In-Reply-To: <444F9E2D.2000901@yahoo.com.au>

Hi,

On Wednesday 26 April 2006 18:22, Nick Piggin wrote:
> Nigel Cunningham wrote:
> > On Wednesday 26 April 2006 12:24, Nick Piggin wrote:
> > 
> >>Rafael J. Wysocki wrote:
> >>
> >>>This means if we freeze bdevs, we'll be able to save all of the LRU pages,
> >>>except for the pages mapped by the current task, without copying.  I think
> >>>we can try to do this, but we'll need a patch to freeze bdevs for this
> >>>purpose. ;-)
> >>
> >>Why not the current task? Does it exit the kernel? Or go through some
> >>get_uesr_pages path?
> > 
> > 
> > I think Rafael is asleep at the mo, so I'll answer for him - he's wanting it 
> > to be compatible with using userspace to control what happens (uswsusp). In 
> > that case, current will be the userspace program that's calling the ioctls to 
> > get processes frozen etc.

Thanks Nigel. :-)

> OK, so what happens if, upon exit from kernel, that userspace task
> subsequently changes some pagecache but doesn't have that mapped? Or
> mmaps something then changes it?

The page cache that is not mapped by anyone is copied before creating the
image and the copy is included in the image.  However there would be a problem
if some page cache mapped by someone else were mapped by the suspending
task after it had exited the kernel.

Fortunately this task is forbidden to open() or mmap() any files at that time
anyway, because it would be likely to corrupt some filesystems if it did.
In fact it must not _touch_ any filesystems after the image has been created.

Greetings,
Rafael

  reply	other threads:[~2006-04-26 21:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 21:55 [RFC][PATCH] swsusp: support creating bigger images Rafael J. Wysocki
2006-04-24 22:16 ` Pavel Machek
2006-04-25  8:26   ` Rafael J. Wysocki
2006-04-25 10:04     ` Pavel Machek
2006-04-25 10:31       ` Rafael J. Wysocki
2006-04-27 15:27         ` Rafael J. Wysocki
2006-04-27 20:55           ` Pavel Machek
2006-04-28  9:19             ` Rafael J. Wysocki
2006-04-28  9:23               ` Pavel Machek
2006-04-25 10:28 ` Nick Piggin
2006-04-25 15:39   ` Rafael J. Wysocki
2006-04-25 20:32     ` Pavel Machek
2006-04-25 21:12       ` Rafael J. Wysocki
2006-04-25 21:18         ` Nigel Cunningham
2006-04-25 22:21           ` Rafael J. Wysocki
2006-04-25 22:24             ` Nigel Cunningham
2006-04-25 22:38               ` Rafael J. Wysocki
2006-04-25 22:25             ` Pavel Machek
2006-04-25 22:30               ` Nigel Cunningham
2006-04-25 22:36                 ` Pavel Machek
2006-04-25 22:43               ` Rafael J. Wysocki
2006-04-26  0:49                 ` Nigel Cunningham
2006-04-30 12:27                   ` Rafael J. Wysocki
2006-05-01  1:49                     ` Nigel Cunningham
2006-05-01 11:20                       ` Rafael J. Wysocki
2006-05-01 22:56                         ` Nigel Cunningham
2006-04-26  2:24             ` Nick Piggin
2006-04-26  3:41               ` Nigel Cunningham
2006-04-26 16:22                 ` Nick Piggin
2006-04-26 21:16                   ` Rafael J. Wysocki [this message]
2006-04-26  8:10               ` Pavel Machek
2006-04-27 19:53     ` [RFC][PATCH] swsusp: support creating bigger images (rev. 2) Rafael J. Wysocki

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=200604262316.44162.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=nigel@suspend2.net \
    --cc=pavel@ucw.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