From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp with highmem, testing wanted
Date: Fri, 26 Mar 2004 11:22:07 +1100 [thread overview]
Message-ID: <1080260526.3068.15.camel@gaston> (raw)
In-Reply-To: <20040325225946.GI2179@elf.ucw.cz>
On Fri, 2004-03-26 at 09:59, Pavel Machek wrote:
> Hi!
>
> > > I'd need to do atomic copy. (Unless someone can guarantee that during
> > > writing to disk, no highmem page is going to be changed...)
> > >
> > > "copy back" during resume is done in assembly, and I'd rather not
> > > dealed with highmem there.
> >
> > Can you make that an option ? The PPC version runs in real mode and
> > can perfectly copy highmem pages (with small tweaks maybe)
>
> What is real mode on PPC? I do not have PPC here, I guess you'd have
> to do that.
MMU OFF, access to entire physical memory. This will not work on
things like pSeries with hypervisor or iSeries, but I could deal with
that if/when needed. I know that x86 with more than 4Gb cannot access
the entire RAM in a linear way though, dunno what other facilities
you have outside of kmap then. But leave the door open to archs that
can do it ;)
> Yes, swsusp2 is faster. It is also 10x more code. We could probably
> stop freeing as soon as half of memory is free; OTOH if memory is
> disk cache, it might be faster to drop it than write to swap, then
> read back [swsusp2 shows its not usually the case, through].
> Pavel
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2004-03-26 0:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 23:57 swsusp with highmem, testing wanted Pavel Machek
2004-03-25 3:28 ` Benjamin Herrenschmidt
[not found] ` <20040325120250.GC300@elf.ucw.cz>
2004-03-25 22:41 ` Benjamin Herrenschmidt
2004-03-25 22:59 ` Pavel Machek
2004-03-25 22:44 ` Nigel Cunningham
2004-03-25 23:54 ` Pavel Machek
2004-03-25 23:06 ` Nigel Cunningham
2004-03-26 0:22 ` Benjamin Herrenschmidt [this message]
2004-03-25 3:48 ` Jeff Chua
[not found] ` <20040325073244.GE3377@suse.de>
[not found] ` <20040325115129.GB300@elf.ucw.cz>
[not found] ` <20040325121418.GK3377@suse.de>
2004-03-25 15:01 ` Pavel Machek
2004-03-25 15:27 ` Jens Axboe
2004-03-25 22:22 ` Pavel Machek
2004-03-26 14:09 ` Jens Axboe
2004-03-26 14:34 ` Pavel Machek
[not found] ` <20040325100339.GN791@holomorphy.com>
2004-03-25 21:59 ` Pavel Machek
2004-03-26 12:03 ` William Lee Irwin III
2004-03-26 12:08 ` Pavel Machek
2004-03-26 12:36 ` William Lee Irwin III
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=1080260526.3068.15.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.