From: Ian Jackson <ian.jackson@citrix.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH v2] tools/libxl: make default of max event channels dependant on vcpus
Date: Mon, 6 Apr 2020 11:47:39 +0100 [thread overview]
Message-ID: <24203.2251.628483.557280@mariner.uk.xensource.com> (raw)
In-Reply-To: <d1b095db-064e-bccf-b55d-d85fecb3045a@suse.com>
Jürgen Groß writes ("Re: [PATCH v2] tools/libxl: make default of max event channels dependant on vcpus"):
> On 06.04.20 11:24, Julien Grall wrote:
> > Large guests on which arch? Which type of guests?
>
> I'm pretty sure this applies to x86 only. I'm not aware of event
> channels being used on ARM for IPIs.
Should this be arch-dependent then ? It seems like the figure is just
a heuristic anyway, and ...
> The resulting number would be larger than today only for guests with
> more than 96 vcpus. So I don't think the additional amount of memory
> is really that problematic.
Julien, are there likely to be any ARM guests now which have anywhere
near that number of vcpus ? If not do we know now what such guests
are likely to be like ?
If this is all hypothetical on ARM it would seem silly to make this
arch-specific for the benefit of ARM given that the ARM implementation
would be entirely guesswork. Maybe we should postpone that
specialisation until we know better what the ARM function should be
like for these large numbers of vcpus.
If ARM folks want to have a different formula for the default then
that is of course fine but I wonder whether this might do ARMk more
harm than good in this case.
Ian.
next prev parent reply other threads:[~2020-04-06 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 8:27 [PATCH v2] tools/libxl: make default of max event channels dependant on vcpus Juergen Gross
2020-04-06 9:24 ` Julien Grall
2020-04-06 10:17 ` Jürgen Groß
2020-04-06 10:37 ` Julien Grall
2020-04-06 10:47 ` Jürgen Groß
2020-04-06 10:52 ` Ian Jackson
2020-04-06 11:00 ` [PATCH v2] tools/libxl: make default of max event channels dependant on vcpus [and 1 more messages] Ian Jackson
2020-04-06 11:03 ` Jürgen Groß
2020-04-06 11:11 ` Jan Beulich
2020-04-06 11:54 ` Jürgen Groß
2020-04-06 12:09 ` Jan Beulich
2020-06-02 11:06 ` Jürgen Groß
2020-06-02 11:12 ` Jan Beulich
2020-06-02 11:23 ` Jürgen Groß
2020-06-02 13:21 ` Jan Beulich
2020-04-06 10:47 ` Ian Jackson [this message]
2020-04-06 10:55 ` [PATCH v2] tools/libxl: make default of max event channels dependant on vcpus Julien Grall
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=24203.2251.628483.557280@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.