public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@digeo.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Hot/cold allocation -- swsusp can not handle hot pages
Date: Sun, 3 Nov 2002 12:14:48 -0800	[thread overview]
Message-ID: <20021103201448.GM23425@holomorphy.com> (raw)
In-Reply-To: <20021103200809.GC27271@elf.ucw.cz>

At some point in the past, Andrew Morton wrote:
>> I'm not really sure what to suggest here.  Emptying the per-cpu
>> page pools would be tricky.  Maybe a swsusp-special page allocator
>> which goes direct to the buddy lists or something.

On Sun, Nov 03, 2002 at 09:08:09PM +0100, Pavel Machek wrote:
> Well, see the patch above. That seems to do the trick for
> me. It seems that even "cold" allocation can give page from per-cpu
> pool. I thought that was a bug?

Not a bug. The semantics only imply a preference for merging, not
a requirement to do so. A direct dequeue-from-buddy method either
by adjusting watermarks or a specialized interface in combination
with per-cpu list shootdown is required to enforce your invariants.


Bill

  reply	other threads:[~2002-11-03 20:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02 18:19 Hot/cold allocation -- swsusp can not handle hot pages Pavel Machek
2002-11-02 18:46 ` William Lee Irwin III
2002-11-02 20:22   ` Pavel Machek
2002-11-02 21:48     ` Andrew Morton
2002-11-03 20:08       ` Pavel Machek
2002-11-03 20:14         ` William Lee Irwin III [this message]
2002-11-03 20:21         ` Andrew Morton
2002-11-03 20:26           ` Pavel Machek
2002-11-03 20:52         ` William Lee Irwin III
2002-11-03 21:22           ` William Lee Irwin III
2002-11-03 22:53           ` 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=20021103201448.GM23425@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --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