From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH 0/2] Eliminate spin locks in the vmbus channel callback path
Date: Tue, 8 Apr 2014 18:45:28 -0700 [thread overview]
Message-ID: <1397007928-13555-1-git-send-email-kys@microsoft.com> (raw)
Currently we map the channel handle to the channel under the protection of
a spin lock. Additionally, we dispatch the channel callback function under the
protection of the channel inbound lock (another spin lock). In some recent
nework performance runs, the time spent acquiring and releasing these locks
were identified as potential bottlenecks. This patch-set gets rid of these
locks by leveraging the interrupt bindings that we support starting with win8.
K. Y. Srinivasan (2):
Drivers: hv: Eliminate the channel spinlock in the callback path
Drivers: hv: vmbus: Implement per-CPU mapping of relid to channel
drivers/hv/channel.c | 16 ++++++++++---
drivers/hv/channel_mgmt.c | 52 ++++++++++++++++++++++++++++++++++++++++----
drivers/hv/connection.c | 35 +++++++++++++++++++++++-------
drivers/hv/hv.c | 2 +
drivers/hv/hyperv_vmbus.h | 5 ++++
include/linux/hyperv.h | 7 ++++++
6 files changed, 100 insertions(+), 17 deletions(-)
--
1.7.4.1
next reply other threads:[~2014-04-09 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 1:45 K. Y. Srinivasan [this message]
2014-04-09 1:45 ` [PATCH 1/2] Drivers: hv: Eliminate the channel spinlock in the " K. Y. Srinivasan
2014-04-09 1:45 ` [PATCH 2/2] Drivers: hv: vmbus: Implement per-CPU mapping of relid to channel K. Y. Srinivasan
2014-04-23 17:54 ` [PATCH 0/2] Eliminate spin locks in the vmbus channel callback path KY Srinivasan
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=1397007928-13555-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
Powered by JetHome