From: Michael Ellerman <mpe@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/mm: Add trace point for tracking hash pte fault
Date: Wed, 28 Jan 2015 17:11:07 +1100 [thread overview]
Message-ID: <1422425467.11009.2.camel@ellerman.id.au> (raw)
In-Reply-To: <87d268v7xm.fsf@linux.vnet.ibm.com>
On Wed, 2015-01-21 at 14:15 +0530, Aneesh Kumar K.V wrote:
> Michael Ellerman <mpe@ellerman.id.au> writes:
>
> > On Tue, 2015-01-20 at 17:05 +0530, Aneesh Kumar K.V wrote:
> >> This enables us to understand how many hash fault we are taking
> >> when running benchmarks.
> >>
> >> For ex:
> >> -bash-4.2# ./perf stat -e powerpc:hash_fault -e page-faults /tmp/ebizzy.ppc64 -S 30 -P -n 1000
> >> ...
> >>
> >> Performance counter stats for '/tmp/ebizzy.ppc64 -S 30 -P -n 1000':
> >>
> >> 1,10,04,075 powerpc:hash_fault
> >> 1,10,03,429 page-faults
> >>
> >> 30.865978991 seconds time elapsed
> >
> > Looks good.
> >
> > Can you attach some test results that show it's not hurting performance when
> > it's disabled.
>
> ebizzy with -S 30 -t 1 -P gave
> 13627 records/s -> Without patch
> 13546 records/s -> With patch with tracepoint disabled
OK. So that's about -0.6%. Are we happy with that? I'm not sure.
Can you do a few more runs and see if that's a stable result.
> random_access_bench gave:
> 1435.979 MB/s -> Without patch
> 1435.29 MB/s -> With patch with tracepoint disabled
That's more like -0.05% which is in the noise.
cheers
next prev parent reply other threads:[~2015-01-28 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:35 [PATCH] powerpc/mm: Add trace point for tracking hash pte fault Aneesh Kumar K.V
2015-01-21 3:07 ` Michael Ellerman
2015-01-21 8:45 ` Aneesh Kumar K.V
2015-01-28 6:11 ` Michael Ellerman [this message]
2015-02-02 10:26 ` Anton Blanchard
2015-02-02 16:21 ` Aneesh Kumar K.V
2015-02-02 22:01 ` Anton Blanchard
2015-02-03 3:07 ` Aneesh Kumar K.V
2015-02-02 16:12 ` Aneesh Kumar K.V
2015-04-02 8:44 ` Aneesh Kumar K.V
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=1422425467.11009.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).