com; vkuzn...@redhat.com;
> jasow...@redhat.com; leann.ogasaw...@canonical.com; K. Y. Srinivasan
> <k...@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,
; jasow...@redhat.com; leann.ogasaw...@canonical.com; K. Y. Srinivasan
>
> Subject: Re: [PATCH 1/1] Drivers: hv: Introduce a policy for controlling
> channel
> affinity
>
> On Wed, Jul 06, 2016 at 06:02:15PM -0700, k...@exchange.microsoft.com
> wrote:
> > From: K. Y. Srin
On Wed, Jul 06, 2016 at 06:02:15PM -0700, k...@exchange.microsoft.com wrote:
> From: K. Y. Srinivasan
>
> Introduce a mechanism to control how channels will be affinitized. We will
> support two policies:
>
> 1. HV_BALANCED: All performance critical channels will be
On Wed, Jul 06, 2016 at 06:02:15PM -0700, k...@exchange.microsoft.com wrote:
> From: K. Y. Srinivasan
>
> 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
From: K. Y. Srinivasan
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
From: K. Y. Srinivasan
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
6 matches
Mail list logo