From: Chao Gao <chao.gao@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH 0/4] mitigate the per-pCPU blocking list may be too long
Date: Wed, 26 Apr 2017 11:30:52 +0800 [thread overview]
Message-ID: <20170426033050.GA77987@skl-2s3.sh.intel.com> (raw)
In-Reply-To: <5900742A020000780015441D@prv-mh.provo.novell.com>
On Wed, Apr 26, 2017 at 02:19:22AM -0600, Jan Beulich wrote:
>>>> On 26.04.17 at 02:52, <chao.gao@intel.com> 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?
I thought randomly distribution is simple and also can meet our
demand. What you said I think is also ok. How about just choose the
CPU which has the shortest list length? I will use this policy in next
version. Will you review this version when you have time? or I can
prepare and send next version directly?
Regarding to the test I do, any other complementary tests do you
think are needed to prove that these patches really mitigate the
issue?
Thanks
Chao
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-26 3:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 0:52 [PATCH 0/4] mitigate the per-pCPU blocking list may be too long Chao Gao
2017-04-26 0:52 ` [PATCH 1/4] xentrace: add TRC_HVM_VT_D_PI_BLOCK Chao Gao
2017-04-26 0:52 ` [PATCH 2/4] VT-d PI: Randomly Distribute entries to all online pCPUs' pi blocking list Chao Gao
2017-04-26 0:52 ` [PATCH 3/4] VT-d PI: Add reference count to pi_desc Chao Gao
2017-04-26 0:52 ` [PATCH 4/4] VT-d PI: Don't add vCPU to PI blocking list for a case Chao Gao
2017-04-26 8:19 ` [PATCH 0/4] mitigate the per-pCPU blocking list may be too long Jan Beulich
2017-04-26 3:30 ` Chao Gao [this message]
2017-04-26 10:52 ` Jan Beulich
2017-04-26 16:39 ` George Dunlap
2017-04-27 0:43 ` Chao Gao
2017-04-27 9:44 ` George Dunlap
2017-04-27 5:02 ` Chao Gao
2017-05-02 5:45 ` Chao Gao
2017-05-03 10:08 ` George Dunlap
2017-05-03 10:21 ` Jan Beulich
2017-05-08 16:15 ` Chao Gao
2017-05-08 8:39 ` Jan Beulich
2017-05-08 16:38 ` Chao Gao
2017-05-08 9:13 ` George Dunlap
2017-05-08 9:24 ` Jan Beulich
2017-05-08 17:37 ` Chao Gao
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=20170426033050.GA77987@skl-2s3.sh.intel.com \
--to=chao.gao@intel.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).