> -----Original Message-----
> From: Xen-devel <xen-devel-boun...@lists.xenproject.org> On Behalf Of Ian
> Jackson
> Sent: 26 November 2019 17:36
> To: George Dunlap <george.dun...@citrix.com>
> Cc: Juergen Gross <jgr...@suse.com>; Stefano Stabellini
> <sstabell...@kernel.org>; Julien Grall <jul...@xen.org>; Wei Liu
> <w...@xen.org>; Paul Durrant <p...@xen.org>; Andrew Cooper
> <andrew.coop...@citrix.com>; Konrad Rzeszutek Wilk
> <konrad.w...@oracle.com>; Marek Marczykowski-Górecki
> <marma...@invisiblethingslab.com>; Hans van Kranenburg <h...@knorrie.org>;
> Jan Beulich <jbeul...@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
