From: Brice Goglin <Brice.Goglin@inria.fr>
To: Andi Kleen <andi@firstfloor.org>
Cc: Stefan Lankes <lankes@lfbs.rwth-aachen.de>,
linux-kernel@vger.kernel.org, Lee.Schermerhorn@hp.com,
linux-numa@vger.kernel.org
Subject: Re: [RFC PATCH 0/4]: affinity-on-next-touch
Date: Mon, 11 May 2009 15:32:01 +0200 [thread overview]
Message-ID: <4A0828D1.4040109@inria.fr> (raw)
In-Reply-To: <87zldjn597.fsf@basil.nowhere.org>
Andi Kleen wrote:
> Stefan Lankes <lankes@lfbs.rwth-aachen.de> writes:
>
>> [Patch 1/4]: Extend the system call madvise with a new parameter
>> MADV_ACCESS_LWP (the same as used in Solaris). The specified memory area
>>
>
> Linux does NUMA memory policies in mbind(), not madvise()
> Also if there's a new NUMA policy it should be in the standard
> Linux NUMA memory policy frame work, not inventing a new one
>
Marking a buffer as "migrate-on-next-touch" is very different from
setting a NUMA policy. Migrate-on-next-touch a temporary flag that is
cleared on the next-touch. It's cleared per page, not per area or
whatever. So marking a VMA as "migrate-on-next-touch" doesn't make much
sense since some pages could already have been migrated (and brought
back to their usual state) while some other are still marked as
migrate-on-next-touch.
Brice
next prev parent reply other threads:[~2009-05-11 13:32 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 8:27 [RFC PATCH 0/4]: affinity-on-next-touch Stefan Lankes
2009-05-11 8:48 ` Dieter an Mey
2009-05-11 13:22 ` Andi Kleen
2009-05-11 13:32 ` Brice Goglin [this message]
2009-05-11 14:54 ` Stefan Lankes
2009-05-11 14:54 ` Stefan Lankes
2009-05-11 16:37 ` Andi Kleen
2009-05-11 17:22 ` Stefan Lankes
2009-06-11 18:45 ` Stefan Lankes
2009-06-12 10:32 ` Andi Kleen
2009-06-12 11:46 ` Stefan Lankes
2009-06-12 12:30 ` Brice Goglin
2009-06-12 13:21 ` Stefan Lankes
2009-06-12 13:48 ` Stefan Lankes
2009-06-16 2:39 ` Lee Schermerhorn
2009-06-16 13:58 ` Stefan Lankes
2009-06-16 14:59 ` Lee Schermerhorn
2009-06-17 1:22 ` KAMEZAWA Hiroyuki
2009-06-17 12:02 ` Lee Schermerhorn
2009-06-17 7:45 ` Stefan Lankes
2009-06-18 4:37 ` Lee Schermerhorn
2009-06-18 19:04 ` Lee Schermerhorn
2009-06-19 15:26 ` Lee Schermerhorn
2009-06-19 15:41 ` Balbir Singh
2009-06-19 15:59 ` Lee Schermerhorn
2009-06-19 21:19 ` Stefan Lankes
2009-06-22 12:34 ` Brice Goglin
2009-06-22 14:24 ` Lee Schermerhorn
2009-06-22 15:28 ` Brice Goglin
2009-06-22 16:55 ` Lee Schermerhorn
2009-06-22 17:06 ` Brice Goglin
2009-06-22 17:59 ` Stefan Lankes
2009-06-22 19:10 ` Brice Goglin
2009-06-22 20:16 ` Stefan Lankes
2009-06-22 20:34 ` Brice Goglin
2009-06-22 14:32 ` Stefan Lankes
2009-06-22 14:56 ` Lee Schermerhorn
2009-06-22 15:42 ` Stefan Lankes
2009-06-22 16:38 ` Lee Schermerhorn
2009-06-16 2:25 ` Lee Schermerhorn
2009-06-20 7:24 ` Brice Goglin
2009-06-22 13:49 ` Lee Schermerhorn
2009-06-16 2:21 ` Lee Schermerhorn
-- strict thread matches above, loose matches on Subject: below --
2009-05-11 14:31 Samuel Thibault
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=4A0828D1.4040109@inria.fr \
--to=brice.goglin@inria.fr \
--cc=Lee.Schermerhorn@hp.com \
--cc=andi@firstfloor.org \
--cc=lankes@lfbs.rwth-aachen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-numa@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.