From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
Dexuan Cui <decui@microsoft.com>
Subject: [PATCH v2 0/6] Drivers: hv: vmbus: fair round robin algorithm for vmbus_get_outgoing_channel()
Date: Mon, 27 Apr 2015 19:04:10 +0200 [thread overview]
Message-ID: <1430154256-26853-1-git-send-email-vkuznets@redhat.com> (raw)
Changes in v2:
- Address Dexuan's review comments:
PATCH 3/6: s,channel,primary_channel;
PATCH 4/6: add a forward declaration instead of moving code around;
PATCH 6/6: fix an off-by-one
- Change the algorithm in PATCH 6/6:
Instead of a simple round robin we first try to find a (sub)channel with
the current_cpu == target_cpu and we fallback to a round robin when we fail
to find one.
K. Y., Dexuan, can you please give it a spin in various testing environments
you have? Thanks!
Original description:
This series is a continuation of the "Drivers: hv: vmbus: Use a round-robin
algorithm for picking the outgoing channel" work. It is supposed to bring two
significant changes:
1) Subchannels for a channel are distributed evenly across all vcpus we have.
Currently we try to distribute all channels (including subchannels) across
all vcpus, this approach doesn't guarantee that the particular channel's
subchannels will be distributed in the same way as we process all offer
requests in some random order. (Patch 05)
2) Channel picking based on the current vcpu is dropped from
vmbus_get_outgoing_channel() in favor of a fair round robin. (Patch 06) (this
is not true anymore, see 'Changes').
Patches 01 - 04 are cleanup/refactoring.
Vitaly Kuznetsov (6):
Drivers: hv: vmbus: unify calls to percpu_channel_enq()
Drivers: hv: vmbus: briefly comment num_sc and next_oc
Drivers: hv: vmbus: decrease num_sc on subchannel removal
Drivers: hv: vmbus: move init_vp_index() call to vmbus_process_offer()
Drivers: hv: vmbus: distribute subchannels among all vcpus
Drivers: hv: vmbus: improve selection of an outgoing channel
drivers/hv/channel_mgmt.c | 127 ++++++++++++++++++++++++++--------------------
include/linux/hyperv.h | 12 +++--
2 files changed, 80 insertions(+), 59 deletions(-)
--
1.9.3
next reply other threads:[~2015-04-27 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:04 Vitaly Kuznetsov [this message]
2015-04-27 17:04 ` [PATCH v2 1/6] Drivers: hv: vmbus: unify calls to percpu_channel_enq() Vitaly Kuznetsov
2015-04-27 17:04 ` [PATCH v2 2/6] Drivers: hv: vmbus: briefly comment num_sc and next_oc Vitaly Kuznetsov
2015-04-27 17:04 ` [PATCH v2 3/6] Drivers: hv: vmbus: decrease num_sc on subchannel removal Vitaly Kuznetsov
2015-04-27 17:04 ` [PATCH v2 4/6] Drivers: hv: vmbus: move init_vp_index() call to vmbus_process_offer() Vitaly Kuznetsov
2015-04-27 17:04 ` [PATCH v2 5/6] Drivers: hv: vmbus: distribute subchannels among all vcpus Vitaly Kuznetsov
2015-04-27 17:04 ` [PATCH v2 6/6] Drivers: hv: vmbus: improve selection of an outgoing channel Vitaly Kuznetsov
2015-04-28 4:30 ` [PATCH v2 0/6] Drivers: hv: vmbus: fair round robin algorithm for vmbus_get_outgoing_channel() Dexuan Cui
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=1430154256-26853-1-git-send-email-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®