From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] powerpc/mm: Add trace point for tracking hash pte fault
Date: Tue, 03 Feb 2015 08:37:35 +0530 [thread overview]
Message-ID: <87pp9r7kw8.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150203090129.5e3c7494@kryten>
Anton Blanchard <anton@samba.org> writes:
> Hi Aneesh,
>
>> yes. We do use jump label. I also verified that looking at .s
>>
>> #APP
>> # 23 "./arch/powerpc/include/asm/jump_label.h" 1
>> 1:
>> nop
>> .pushsection __jump_table, "aw"
>> .llong 1b, .L201, __tracepoint_hash_fault+8 #,
>> .popsection
>>
>> # 0 "" 2
>
> So we insert a single nop, and the slow path is in another section. I'd
> be surprised if we could measure this, unless the nop causes a branch
> target alignment issue the slow path caused some hot path icache layout
> issues.
>
>> Without patch
>> sys: 0m11.2425
>>
>> With patch:
>> sys: 0m11.3258
>>
>> ie, a -0.7% impact
>>
>> If that impact is high we could possibly put that tracepoint within
>> #ifdef CONFIG_DEBUG_VM ?
>
> Did the real time change? I'd be careful about comparing based on
> system time.
Yes it did.
11.8769 with patch
11.7924 without patch
I will look at the perf stat data difference between the both runs and update.
-aneesh
next prev parent reply other threads:[~2015-02-03 3:08 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
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 [this message]
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=87pp9r7kw8.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=anton@samba.org \
--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).