[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 0/4] mitigate the per-pCPU blocking list may be too long

To: "Chao Gao" <chao.gao@xxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Wed, 26 Apr 2017 02:19:22 -0600
Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx, Jun Nakajima <jun.nakajima@xxxxxxxxx>
Delivery-date: Wed, 26 Apr 2017 08:19:36 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 26.04.17 at 02:52, <chao.gao@xxxxxxxxx> wrote:
> Patch 2/4 randomly distritbutes entries (vCPUs) among all oneline
> pCPUs, which can theoretically decrease the maximum of #entry
> in the list by N times. N is #pCPU.

Why randomly? Shouldn't current list length determine which CPU(s)
to prefer?

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH 0/4] mitigate the per-pCPU blocking list may be too long
  - From: Chao Gao

References:
- [Xen-devel] [PATCH 0/4] mitigate the per-pCPU blocking list may be too long
  - From: Chao Gao

Prev by Date: Re: [Xen-devel] [PATCH 01/10] xen/arm: vpl011: Add pl011 uart emulation in Xen
Next by Date: [Xen-devel] [ovmf test] 107702: all pass - PUSHED
Previous by thread: [Xen-devel] [PATCH 4/4] VT-d PI: Don't add vCPU to PI blocking list for a case
Next by thread: Re: [Xen-devel] [PATCH 0/4] mitigate the per-pCPU blocking list may be too long
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.