From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.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 10:54:21 +0530 [thread overview]
Message-ID: <55A34B85.3090902@linux.vnet.ibm.com> (raw)
In-Reply-To: <1436512241.4895.2.camel@neuling.org>
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.
(A) Floating point context switches (context_switch2 --fp 0 0)
Without the patch With the patch
================= ==============
320216 323460
324596 318448
321206 316540
321308 316650
318904 316478
(B) AltiVec context switches (context_switch2 --altivec 0 0)
Without the patch With the patch
================= ==============
352012 342028
345894 345156
354604 345534
354020 354714
353936 364814
(C) Vector context switches (context_switch2 --vector 0 0)
Without the patch With the patch
================= ==============
354496 344296
361386 346822
361856 354932
344906 348722
343288 355014
next prev parent reply other threads:[~2015-07-13 5:24 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 [this message]
2015-07-13 5:41 ` Michael Ellerman
2015-07-13 6:46 ` Anshuman Khandual
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=55A34B85.3090902@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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).