From: Vijay Kumar <vijay.ac.kumar@oracle.com>
To: davem@davemloft.net, sparclinux@vger.kernel.org
Cc: rob.gardner@oracle.com, anthony.yznaga@oracle.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] sparc64: Use low latency path to resume idle cpu
Date: Sat, 8 Jul 2017 14:23:42 -0600 [thread overview]
Message-ID: <1499545424-415240-1-git-send-email-vijay.ac.kumar@oracle.com> (raw)
cpu_poke is a low latency path to resume the target cpu if suspended
using cpu_yield. Use cpu poke to resume cpu if supported by hypervisor.
hackbench results (lower is better):
Number of
Process: w/o fix with fix
1 0.012 0.010
10 0.021 0.019
100 0.151 0.148
Vijay Kumar (2):
sparc64: Add a new hypercall CPU_POKE
sparc64: Use cpu_poke to resume idle cpu
arch/sparc/include/asm/hypervisor.h | 17 ++++++++
arch/sparc/include/asm/smp_64.h | 5 ++
arch/sparc/kernel/hvapi.c | 9 ++++
arch/sparc/kernel/hvcalls.S | 11 +++++
arch/sparc/kernel/process_64.c | 7 +++-
arch/sparc/kernel/setup_64.c | 1 +
arch/sparc/kernel/smp_64.c | 75 +++++++++++++++++++++++++++++++++-
7 files changed, 121 insertions(+), 4 deletions(-)
--
next reply other threads:[~2017-07-08 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 20:23 Vijay Kumar [this message]
2017-07-08 20:23 ` [PATCH 1/2] sparc64: Add a new hypercall CPU_POKE Vijay Kumar
2017-07-08 20:23 ` [PATCH 2/2] sparc64: Use cpu_poke to resume idle cpu Vijay Kumar
2017-07-20 19:58 ` David Miller
2017-07-21 2:47 ` Vijay Kumar
2017-07-20 19:57 ` [PATCH 0/2] sparc64: Use low latency path " David Miller
2017-07-21 2:44 ` Vijay Kumar
2017-07-21 2:55 ` David Miller
2017-07-21 3:36 ` Vijay Kumar
2017-07-21 3:45 ` David Miller
2017-07-21 4:11 ` Vijay Kumar
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=1499545424-415240-1-git-send-email-vijay.ac.kumar@oracle.com \
--to=vijay.ac.kumar@oracle.com \
--cc=anthony.yznaga@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.gardner@oracle.com \
--cc=sparclinux@vger.kernel.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).