From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
andi.kleen@intel.com, Prarit Bhargava <prarit@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"menage@google.com" <menage@google.com>,
Pavel Emelianov <xemul@openvz.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Help Resource Counters Scale Better (v3)
Date: Mon, 10 Aug 2009 14:06:02 +0530 [thread overview]
Message-ID: <20090810083602.GA7176@balbir.in.ibm.com> (raw)
In-Reply-To: <20090810152205.d37d8e2f.kamezawa.hiroyu@jp.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-08-10 15:22:05]:
> On Mon, 10 Aug 2009 14:45:59 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> > > Do you agree?
> >
> > Ok. Config is enough at this stage.
> >
> > The last advice for merge is, it's better to show the numbers or
> > ask someone who have many cpus to measure benefits. Then, Andrew can
> > know how this is benefical.
> > (My box has 8 cpus. But maybe your IBM collaegue has some bigger one)
> >
> > In my experience (in my own old trial),
> > - lock contention itself is low. not high.
> > - but cacheline-miss, pingpong is very very frequent.
> >
> > Then, this patch has some benefit logically but, in general,
> > File-I/O, swapin-swapout, page-allocation/initalize etc..dominates
> > the performance of usual apps. You'll have to be careful to select apps
> > to measure the benfits of this patch by application performance.
> > (And this is why I don't feel so much emergency as you do)
> >
>
> Why I say "I want to see the numbers" again and again is that
> this is performance improvement with _bad side effect_.
> If this is an emergent trouble, and need fast-track, which requires us
> "fix small problems later", plz say so.
>
OK... I finally got a bigger machine (24 CPUs). I ran a simple
program called parallel_pagefault, which does pagefault's in parallel
(runs on every other CPU) and allocates 10K pages and touches the
data allocated, unmaps and repeats the process. I ran the program
for 300 seconds. With the patch, I was able to fault in twice
the number of pages as I was able to without the patch. I used
perf tool from tools/perf in the kernel
With patch
Performance counter stats for '/home/balbir/parallel_pagefault':
7188177.405648 task-clock-msecs # 23.926 CPUs
423130 context-switches # 0.000 M/sec
210 CPU-migrations # 0.000 M/sec
49851597 page-faults # 0.007 M/sec
5900210219604 cycles # 820.821 M/sec
424658049425 instructions # 0.072 IPC
7867744369 cache-references # 1.095 M/sec
2882370051 cache-misses # 0.401 M/sec
300.431591843 seconds time elapsed
Without Patch
Performance counter stats for '/home/balbir/parallel_pagefault':
7192804.124144 task-clock-msecs # 23.937 CPUs
424691 context-switches # 0.000 M/sec
267 CPU-migrations # 0.000 M/sec
28498113 page-faults # 0.004 M/sec
5826093739340 cycles # 809.989 M/sec
408883496292 instructions # 0.070 IPC
7057079452 cache-references # 0.981 M/sec
3036086243 cache-misses # 0.422 M/sec
300.485365680 seconds time elapsed
--
Balbir
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-08-10 8:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 22:12 Help Resource Counters Scale Better (v2) Balbir Singh
2009-08-08 1:11 ` KAMEZAWA Hiroyuki
2009-08-08 6:05 ` Balbir Singh
2009-08-08 7:38 ` KAMEZAWA Hiroyuki
2009-08-09 12:15 ` Help Resource Counters Scale Better (v3) Balbir Singh
2009-08-10 0:32 ` KAMEZAWA Hiroyuki
2009-08-10 0:43 ` KAMEZAWA Hiroyuki
2009-08-10 5:22 ` Balbir Singh
2009-08-10 5:30 ` Balbir Singh
2009-08-10 5:45 ` KAMEZAWA Hiroyuki
2009-08-10 6:22 ` KAMEZAWA Hiroyuki
2009-08-10 7:41 ` Balbir Singh
2009-08-10 8:36 ` Balbir Singh [this message]
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=20090810083602.GA7176@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=prarit@redhat.com \
--cc=xemul@openvz.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