From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wl@xen.org>
Subject: Re: [Xen-devel] [PATCH v1] libxl: remove limit for default number of event channels
Date: Fri, 27 Mar 2020 15:37:35 +0100 [thread overview]
Message-ID: <20200327143735.GA4443@aepfle.de> (raw)
In-Reply-To: <24190.3426.470473.335250@mariner.uk.xensource.com>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
On Fri, Mar 27, Ian Jackson wrote:
> This seems likely to be right, but: what is the default in Xen ? Is
> it sufficiently tight to stop a guest using too many resources ?
The value of d->max_evtchns will be either 4k or 128k.
AFAICS no extra resources are allocated with the changed value.
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-27 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 14:22 [Xen-devel] [PATCH v1] libxl: remove limit for default number of event channels Olaf Hering
2020-03-27 14:27 ` Ian Jackson
2020-03-27 14:37 ` Olaf Hering [this message]
2020-03-27 16:13 ` Jan Beulich
2020-03-27 16:50 ` 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=20200327143735.GA4443@aepfle.de \
--to=olaf@aepfle.de \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@citrix.com \
--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.