From: Ingo Molnar <mingo@elte.hu>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Andrew Morton <akpm@linux-foundation.org>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"menage@google.com" <menage@google.com>,
xemul@openvz.org, prarit@redhat.com, andi.kleen@intel.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [UPDATED][PATCH][mmotm] Help Root Memory Cgroup Resource Counters Scale Better (v5)
Date: Sat, 15 Aug 2009 16:26:44 +0200 [thread overview]
Message-ID: <20090815142644.GC15941@elte.hu> (raw)
In-Reply-To: <20090814020122.GL5087@balbir.in.ibm.com>
* Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> * Ingo Molnar <mingo@elte.hu> [2009-08-13 10:35:24]:
>
> >
> > * Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> >
> > > Without Patch
> > >
> > > Performance counter stats for '/home/balbir/parallel_pagefault':
> > >
> > > 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
> >
> > > With this patch applied
> > >
> > > Performance counter stats for '/home/balbir/parallel_pagefault':
> > >
> > > 5957054385619 cycles # 828.333 M/sec
> > > 1058117350365 instructions # 0.178 IPC
> > > 9161776218 cache-references # 1.274 M/sec
> > > 1920494280 cache-misses # 0.267 M/sec
> >
> > Nice how the instruction count and the IPC value incraesed, and the
> > cache-miss count decreased.
> >
> > Btw., a 'perf stat' suggestion: you can also make use of built-in
> > error bars via repeating parallel_pagefault N times:
> >
> > aldebaran:~> perf stat --repeat 3 /bin/ls
>
> Ingo, with the repeat experiements I see
>
> 7192354.545647 task-clock-msecs # 23.955 CPUs ( +- 0.002% )
> 425627 context-switches # 0.000 M/sec ( +- 0.333% )
> 155 CPU-migrations # 0.000 M/sec ( +- 10.897% )
> 95336481 page-faults # 0.013 M/sec ( +- 0.085% )
> 5951929070187 cycles # 827.536 M/sec ( +- 0.009% )
> 1058312583796 instructions # 0.178 IPC ( +- 0.076% )
> 9616609083 cache-references # 1.337 M/sec ( +- 2.536% )
> 1952367514 cache-misses # 0.271 M/sec ( +- 0.156% )
>
> 300.246532761 seconds time elapsed ( +- 0.002% )
>
> Except for the CPU migrations and the cache references, all the
> other parameters seem to be well within an acceptable error range.
Yeah, nice!
Ingo
--
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>
next prev parent reply other threads:[~2009-08-15 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 6:55 [PATCH][mmotm] " Balbir Singh
2009-08-13 7:26 ` Daisuke Nishimura
2009-08-13 8:02 ` [UPDATED][PATCH][mmotm] " Balbir Singh
2009-08-13 8:35 ` Ingo Molnar
2009-08-13 8:43 ` Balbir Singh
2009-08-14 2:01 ` Balbir Singh
2009-08-15 14:26 ` Ingo Molnar [this message]
2009-08-13 11:12 ` Daisuke Nishimura
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=20090815142644.GC15941@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--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