[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A3FD721.3050606@inria.fr>
Date: Mon, 22 Jun 2009 21:10:25 +0200
From: Brice Goglin <Brice.Goglin@...ia.fr>
To: Stefan Lankes <lankes@...s.rwth-aachen.de>
CC: Lee Schermerhorn <Lee.Schermerhorn@...com>,
'Andi Kleen' <andi@...stfloor.org>,
linux-kernel@...r.kernel.org, linux-numa@...r.kernel.org,
Boris Bierbaum <boris@...s.RWTH-Aachen.DE>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: [RFC PATCH 0/4]: affinity-on-next-touch
Stefan Lankes wrote:
> I am not able to reconstruct any performance drawbacks on my system.
> Could you send me your low-level benchmark?
It's attached. As you may see, it's fairly trivial. It just does several
iterations of mbind+touch_all_pages for different power-of-two buffer
sizes. Just replace mbind with madvise in the inner loop if you want to
try with your affinit-on-next-touch.
Which kernels are you using when comparing your next-touch
implementation with Lee's patchset?
Brice
View attachment "next-touch-mof-cost.c" of type "text/x-csrc" (2045 bytes)
Powered by blists - more mailing lists