From: Stefan Lankes <lankes@lfbs.rwth-aachen.de>
To: 'Andi Kleen' <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, Lee.Schermerhorn@hp.com,
linux-numa@vger.kernel.org,
Boris Bierbaum <boris@lfbs.rwth-aachen.de>,
'Brice Goglin' <Brice.Goglin@inria.fr>
Subject: RE: [RFC PATCH 0/4]: affinity-on-next-touch
Date: Fri, 12 Jun 2009 13:46:37 +0200 [thread overview]
Message-ID: <004001c9eb53$71991300$54cb3900$@rwth-aachen.de> (raw)
In-Reply-To: <20090612103251.GJ25568@one.firstfloor.org>
> > I analyze Lee Schermerhorn's migrate memory on cpu migration patches
> > (http://free.linux.hp.com/~lts/Patches/PageMigration/). I think that
> Lee
> > Schermerhorn add similar functionalities to the kernel. He called the
> > "affinity-on-next-touch" functionality "migrate_on_fault" and uses in
> his
> > patches the normal NUMA memory policies. Therefore, his solution fits
> better
> > to the Linux kernel. I tested his patches with our test applications
> and got
> > nearly the same performance results.
>
> That's great to know.
>
> I didn't think he had a per process setting though, did he?
He enables the support of migration-on-fault via cpusets (echo 1 >
/dev/cpuset/migrate_on_fault).
Afterwards, every process could initiate migration-on-fault via mbind(...,
MPOL_MF_MOVE|MPOL_MF_LAZY).
> > I found only patches for the kernel 2.6.25-rc2-mm1. Does someone
> develop
> > these patches further?
>
> Not to much knowledge. Maybe Lee will pick them up again now that there
> are more use cases.
>
> If he doesn't have time maybe you could update them?
We are planning to work in this area. I think that I could update these
patches.
At least, I am able to support Lee.
Stefan
next prev parent reply other threads:[~2009-06-12 11:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000c01c9d212$4c244720$e46cd560$@rwth-aachen.de>
2009-05-11 13:22 ` [RFC PATCH 0/4]: affinity-on-next-touch Andi Kleen
2009-05-11 13:32 ` Brice Goglin
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 [this message]
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
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='004001c9eb53$71991300$54cb3900$@rwth-aachen.de' \
--to=lankes@lfbs.rwth-aachen.de \
--cc=Brice.Goglin@inria.fr \
--cc=Lee.Schermerhorn@hp.com \
--cc=andi@firstfloor.org \
--cc=boris@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).