From: KY Srinivasan <kys@microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"leann.ogasawara@canonical.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 17:56:42 +0000 [thread overview]
Message-ID: <DM2PR0301MB0783ABC11A1AA5DDA334FFACA0E30@DM2PR0301MB0783.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20160831104409.GA22845@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Wednesday, August 31, 2016 4:14 PM
> To: KY Srinivasan <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
>
> 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 :(
>
I will fix this and resend.
K. Y
prev parent reply other threads:[~2016-08-31 17:56 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
2016-08-31 17:56 ` KY Srinivasan [this message]
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=DM2PR0301MB0783ABC11A1AA5DDA334FFACA0E30@DM2PR0301MB0783.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@exchange.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).