From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH V2] powerpc/irq: Enable some more exceptions in /proc/interrupts interface
Date: Mon, 13 Jul 2015 12:16:39 +0530 [thread overview]
Message-ID: <55A35ECF.5050106@linux.vnet.ibm.com> (raw)
In-Reply-To: <1436766076.15957.0.camel@ellerman.id.au>
On 07/13/2015 11:11 AM, Michael Ellerman wrote:
> On Mon, 2015-07-13 at 10:54 +0530, Anshuman Khandual wrote:
>> On 07/10/2015 12:40 PM, Michael Neuling wrote:
>>> What's the performance impact of this? If you run this test with --fp,
>>> --altivec or --vector what is the impact of adding this patch?
>>>
>>> http://ozlabs.org/~anton/junkcode/context_switch2.c
>>>
>>> eg
>>> ./context_switch2 --fp 0 0
>>
>> Please find the results here which looks similar with or without
>> the patch being applied.
>
> No they don't look similar with or without.
>
>> (A) Floating point context switches (context_switch2 --fp 0 0)
>
> If you just sort them you see:
>
> 316478 after
> 316540 after
> 316650 after
> 318448 after
> 318904 before
> 320216 before
> 321206 before
> 321308 before
> 323460 after
> 324596 before
>
>
> It looks like ~1% degradation. Please run the test more times (maybe 1000) and
> see how the numbers look.
Average of 1000 iterations looks better.
With the patch : 322599.57 (Average of 1000 results)
Without the patch : 320464.924 (Average of 1000 results)
prev parent reply other threads:[~2015-07-13 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 9:46 [PATCH V2] powerpc/irq: Enable some more exceptions in /proc/interrupts interface Anshuman Khandual
2015-07-10 7:10 ` Michael Neuling
2015-07-13 5:24 ` Anshuman Khandual
2015-07-13 5:41 ` Michael Ellerman
2015-07-13 6:46 ` Anshuman Khandual [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=55A35ECF.5050106@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).