From: "Durrant, Paul" <pdurrant@amazon.com>
To: Ian Jackson <ian.jackson@citrix.com>,
George Dunlap <george.dunlap@citrix.com>
Cc: "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>, "Wei Liu" <wl@xen.org>,
"Paul Durrant" <paul@xen.org>,
"Andrew Cooper" <Andrew.Cooper3@citrix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Hans van Kranenburg" <hans@knorrie.org>,
"Jan Beulich" <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH for-4.13 2/2] Rationalize max_grant_frames and max_maptrack_frames handling
Date: Wed, 27 Nov 2019 08:42:06 +0000 [thread overview]
Message-ID: <c95b8096d1054d88bce16310aafe978a@EX13D32EUC003.ant.amazon.com> (raw)
In-Reply-To: <24029.25218.75565.126333@mariner.uk.xensource.com>
> -----Original Message-----
> From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Ian
> Jackson
> Sent: 26 November 2019 17:36
> To: George Dunlap <george.dunlap@citrix.com>
> Cc: Juergen Gross <jgross@suse.com>; Stefano Stabellini
> <sstabellini@kernel.org>; Julien Grall <julien@xen.org>; Wei Liu
> <wl@xen.org>; Paul Durrant <paul@xen.org>; Andrew Cooper
> <Andrew.Cooper3@citrix.com>; Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com>; Marek Marczykowski-Górecki
> <marmarek@invisiblethingslab.com>; Hans van Kranenburg <hans@knorrie.org>;
> Jan Beulich <jbeulich@suse.com>; xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] [PATCH for-4.13 2/2] Rationalize max_grant_frames
> and max_maptrack_frames handling
>
> George Dunlap writes ("[PATCH for-4.13 2/2] Rationalize max_grant_frames
> and max_maptrack_frames handling"):
> > Xen used to have single, system-wide limits for the number of grant
> > frames and maptrack frames a guest was allowed to create. Increasing
> > or decreasing this single limit on the Xen command-line would change
> > the limit for all guests on the system.
>
> If I am not mistaken, this is an important change to have.
>
It is, and many thanks to George for picking this up.
> I have seen reports of users who ran out of grant/maptrack frames
> because of updates to use multiring protocols etc. The error messages
> are not very good and the recommended workaround has been to increase
> the default limit on the hypervisor command line.
>
> It is important that we don't break that workaround!
Alas it has apparently been broken for several releases now :-(
Paul
>
> Thanks,
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-27 8:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 17:17 [Xen-devel] [PATCH for-4.13 1/2] python/xc.c: Remove trailing whitespace George Dunlap
2019-11-26 17:17 ` [Xen-devel] [PATCH for-4.13 2/2] Rationalize max_grant_frames and max_maptrack_frames handling George Dunlap
2019-11-26 17:30 ` George Dunlap
2019-11-27 4:34 ` Jürgen Groß
2019-11-27 12:07 ` George Dunlap
2019-11-27 12:15 ` Jürgen Groß
2019-11-26 17:32 ` Durrant, Paul
2019-11-26 17:36 ` Ian Jackson
2019-11-27 8:42 ` Durrant, Paul [this message]
2019-11-27 11:10 ` Ian Jackson
2019-11-27 11:13 ` Durrant, Paul
2019-11-27 22:32 ` Hans van Kranenburg
2019-11-28 5:57 ` Jürgen Groß
2019-11-28 14:54 ` George Dunlap
2019-11-28 15:33 ` Hans van Kranenburg
2019-11-28 15:43 ` Jürgen Groß
2019-11-27 4:32 ` Jürgen Groß
2019-11-27 9:25 ` Jan Beulich
2019-11-27 9:38 ` Jürgen Groß
2019-11-27 10:40 ` George Dunlap
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=c95b8096d1054d88bce16310aafe978a@EX13D32EUC003.ant.amazon.com \
--to=pdurrant@amazon.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=hans@knorrie.org \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=marmarek@invisiblethingslab.com \
--cc=paul@xen.org \
--cc=sstabellini@kernel.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.