From: Pavel Machek <pavel@ucw.cz>
To: Andy Isaacson <adi@hexapodia.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Some highmem pages still in use after shrink_all_memory()?
Date: Mon, 8 Mar 2004 10:13:24 +0100 [thread overview]
Message-ID: <20040308091324.GA209@elf.ucw.cz> (raw)
In-Reply-To: <20040308063639.GA20793@hexapodia.org>
On Po 08-03-04 00:36:39, Andy Isaacson wrote:
> On Sun, Mar 07, 2004 at 04:40:52PM -0800, Andrew Morton wrote:
> > Pavel Machek <pavel@ucw.cz> wrote:
> > > For swsusp, I need to free as much memory as possible. Well, and it
> > > would be great if no highmem pages remained, so that I would not have
> > > to deal with that. Is that possible?
> >
> > No, it isn't. There are pagetable pages and mlocked user pages which we
> > cannot do anything with.
> >
> > We could perhaps swap out the mlocked pages anyway if a suspend is in
> > progress, but the highmem pagetable pages are not presently reclaimed
> > by the VM.
>
> Note that there are some applications for which it is a *bug* if an
> mlocked page gets written out to magnetic media. (gpg, for example.)
Well, but that can not be solved. During suspend-to-disk, data (by
definition) go to magnetic media. We could block suspend, and we could
kill such application....
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-08 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:49 Some highmem pages still in use after shrink_all_memory()? Pavel Machek
2004-03-08 0:40 ` Andrew Morton
2004-03-08 6:36 ` Andy Isaacson
2004-03-08 5:41 ` Nigel Cunningham
2004-03-08 9:13 ` Pavel Machek [this message]
2004-03-08 9:39 ` Arjan van de Ven
2004-03-08 15:09 ` Chris Friesen
2004-03-08 15:16 ` Arjan van de Ven
2004-03-08 15:35 ` Chris Friesen
2004-03-08 17:54 ` Zwane Mwaikambo
2004-03-08 16:36 ` Andy Isaacson
2004-03-08 18:34 ` Pavel Machek
2004-03-08 18:52 ` Andy Isaacson
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=20040308091324.GA209@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=adi@hexapodia.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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.