From: Andi Kleen <ak@suse.de>
To: linux-mm@kvack.org
Subject: Re: [PATCH] Add page migration support via swap to the NUMA policy layer
Date: Sun, 16 Oct 2005 10:56:06 +0200 [thread overview]
Message-ID: <200510161056.07050.ak@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 50 bytes --]
[original mail had a mistyped linux-mm address]
[-- Attachment #2: Mail Delivery System <MAILER-DAEMON@suse.de>: Undelivered Mail Returned to Sender --]
[-- Type: message/rfc822, Size: 5035 bytes --]
[-- Attachment #2.1.1: Notification --]
[-- Type: text/plain, Size: 605 bytes --]
This is the Postfix program at host mx2.suse.de.
I'm sorry to have to inform you that your message could not be
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The Postfix program
<linux-mm@vger.kernel.org>: host vger.kernel.org[209.132.176.167] said: 554
5.0.0 Hi [195.135.220.15], unresolvable address:
<linux-mm@vger.kernel.org>; nosuchuser; linux-mm@vger.kernel.org (in reply
to RCPT TO command)
[-- Attachment #2.1.2: Delivery report --]
[-- Type: message/delivery-status, Size: 465 bytes --]
[-- Attachment #2.1.3: Undelivered Message --]
[-- Type: message/rfc822, Size: 1756 bytes --]
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: lhms-devel@lists.sourceforge.net, linux-mm@vger.kernel.org
Subject: Re: [PATCH] Add page migration support via swap to the NUMA policy layer
Date: Thu, 13 Oct 2005 20:47:03 +0200
Message-ID: <200510132047.03892.ak@suse.de>
On Thursday 13 October 2005 20:15, Christoph Lameter wrote:
> This patch adds page migration support to the NUMA policy layer. An additional
> flag MPOL_MF_MOVE is introduced for mbind. If MPOL_MF_MOVE is specified then
> pages that do not conform to the memory policy will be evicted from memory.
> When they get pages back in new pages will be allocated following the numa policy.
That part looks ok.
>
> In addition this also adds a move_pages function that may be used from outside
> of the policy layer to move pages between nodes (needed by the cpuset support
> and the /proc interface). The design is intended to support future direct page
> migration without going through swap space.
Please split that out and resubmit if there are really other users
(what /proc support?)
> + WARN_ON(isolate_lru_page(page, pagelist) == 0);
WARN_ONs are not supposed to have side effects.
-Andi
next reply other threads:[~2005-10-16 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 8:56 Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-13 18:15 Christoph Lameter
2005-10-13 18:16 ` Christoph Lameter
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=200510161056.07050.ak@suse.de \
--to=ak@suse.de \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox