From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/mm: Add trace point for tracking hash pte fault
Date: Wed, 21 Jan 2015 14:15:09 +0530 [thread overview]
Message-ID: <87d268v7xm.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1421809627.4900.1.camel@ellerman.id.au>
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
12408 records/s -> With patch with tracepoint enabled.
perf stat gave the below data for the above run.
22,38,284 page-faults
22,38,291 powerpc:hash_fault
I also used random_access_bench that Anton wrote, it actually
create lots of hash fault. A simple run gives.
(random_access_bench -o load -g -i -t 10 16G)
1,888 page-faults
2,64,283 powerpc:hash_fault
random_access_bench gave:
1435.979 MB/s -> Without patch
1435.29 MB/s -> With patch with tracepoint disabled
1434.75 MB/s -> With patch with tracepoint enabled.
-aneesh
next prev parent reply other threads:[~2015-01-21 8:45 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 [this message]
2015-01-28 6:11 ` Michael Ellerman
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=87d268v7xm.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.