From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Lankes <lankes@lfbs.rwth-aachen.de>
Subject: RE: [RFC PATCH 0/4]: affinity-on-next-touch
Date: Mon, 11 May 2009 19:22:31 +0200
Message-ID: <000301c9d25d$113c0f30$33b42d90$@rwth-aachen.de>
References: <000c01c9d212$4c244720$e46cd560$@rwth-aachen.de>
 <87zldjn597.fsf@basil.nowhere.org>
 <001501c9d248$69e2a870$3da7f950$@rwth-aachen.de>
 <20090511163719.GA19296@one.firstfloor.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7BIT
Return-path: <linux-numa-owner@vger.kernel.org>
In-reply-to: <20090511163719.GA19296@one.firstfloor.org>
Content-language: de
Sender: linux-numa-owner@vger.kernel.org
List-ID: <linux-numa.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: 'Andi Kleen' <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, Lee.Schermerhorn@hp.com, linux-numa@vger.kernel.org, brice.goglin@inria.fr, "'Terboven, Christian'" <terboven@rz.rwth-aachen.de>, anmey@rz.rwth-aachen.de, Boris Bierbaum <boris@lfbs.rwth-aachen.de>



> -----Original Message-----
> From: Andi Kleen [mailto:andi@firstfloor.org]
> Sent: Monday, May 11, 2009 6:37 PM
> To: Stefan Lankes
> Cc: 'Andi Kleen'; linux-kernel@vger.kernel.org;
> Lee.Schermerhorn@hp.com; linux-numa@vger.kernel.org;
> brice.goglin@inria.fr; 'Terboven, Christian'; anmey@rz.rwth-aachen.de;
> 'Boris Bierbaum'
> Subject: Re: [RFC PATCH 0/4]: affinity-on-next-touch
> 
> > By default, mbind only has an effect on new allocations. I think that
> this
> 
> Nope, it affects existing pages too, it can even move pages
> if you ask for it.
> 

I know this possibility. I thought that "affinity-on-next-touch" fit better
to madvise. Brice told already the technical reasons for preferring of
madvise.

> > For instance, Norden's PDE solvers using adaptive mesh refinements
> (AMR) [1]
> > is an application with a dynamic access pattern. We use this example
> to
> > evaluate the performance of our patch. We ran this solver on our
> > quad-socket, dual-core Opteron 875 (2.2GHz) system running CentOS
> 5.2. The
> > code was already optimized for NUMA architectures. Before the arrays
> are
> > initialized, the threads are bound to one core. In our test case, the
> solver
> > needs 5318s. If we use our kernel extension, the solver needs 4489s.
> 
> Okay that sounds like good numbers.
> 
> > Currently, we are testing some other apps.
> 
> Please keep the list updated.
> 

I will do it.

Stefan