From: Greg KH <gregkh@linuxfoundation.org>
To: kys@microsoft.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
"K. Y. Srinivasan" <kys@exchange.microsoft.com>
Subject: Re: [PATCH 1/1] Drivers: hv: Introduce a policy for controlling channel affinity
Date: Wed, 31 Aug 2016 12:44:09 +0200 [thread overview]
Message-ID: <20160831104409.GA22845@kroah.com> (raw)
In-Reply-To: <1467853335-9374-1-git-send-email-kys@exchange.microsoft.com>
On Wed, Jul 06, 2016 at 06:02:15PM -0700, kys@exchange.microsoft.com wrote:
> From: K. Y. Srinivasan <kys@exchange.microsoft.com>
>
> Introduce a mechanism to control how channels will be affinitized. We will
> support two policies:
>
> 1. HV_BALANCED: All performance critical channels will be dstributed
> evenly amongst all the available NUMA nodes. Once the Node is assigned,
> we will assign the CPU based on a simple round robin scheme.
>
> 2. HV_LOCALIZED: Only the primary channels are distributed across all
> NUMA nodes. Sub-channels will be in the same NUMA node as the primary
> channel. This is the current behaviour.
>
> The default policy will be the HV_BALANCED as it can minimize the remote
> memory access on NUMA machines with applications that span NUMA nodes.
>
> Signed-off-by: K. Y. Srinivasan <kys@exchange.microsoft.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/hv/channel_mgmt.c | 68 +++++++++++++++++++++++++-------------------
> include/linux/hyperv.h | 23 +++++++++++++++
> 2 files changed, 62 insertions(+), 29 deletions(-)
Also doesn't apply cleanly :(
next prev parent reply other threads:[~2016-08-31 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 1:02 [PATCH 1/1] Drivers: hv: Introduce a policy for controlling channel affinity kys
2016-08-31 10:44 ` Greg KH [this message]
2016-08-31 17:56 ` 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=20160831104409.GA22845@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@exchange.microsoft.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.com \
/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).