From: Ian Campbell <ian.campbell@citrix.com>
To: <netdev@vger.kernel.org>, David Miller <davem@davemloft.net>
Cc: xen-devel <xen-devel@lists.xen.org>,
Wei Liu <wei.liu2@citrix.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: stable backport of 3 xen multiqueue network dev fixes
Date: Thu, 21 Jan 2016 11:58:10 +0000 [thread overview]
Message-ID: <1453377490.4320.16.camel@citrix.com> (raw)
Hi Dave,
Please could you queue these three:
32a8440 xen-netfront: respect user provided max_queues
4c82ac3 xen-netback: respect user provided max_queues
ca88ea1 xen-netfront: update num_queues to real created
for stable backports to at least 4.1. Multiqueue was added in v3.16 so I
think they could all go to LTS that far back.
Users are tripping over issues in the field with exhausting the number of
Xen grant entries available to guests when creating large numbers of queues
(which happens with guests with >=32 VCPUs).
ca88ea1 is a fix which causes the failure to allocate grants for all of the
desired queues gracefully, rather than crashing or failing to pass any
traffic.
32a8440 and 4c82ac3 fix the handling of the module parameters on both ends
so that users can choose to have fewer queues than p/vcpus if they like,
which would have been an effective workaround for the issue solved by
ca88ea1 if that hadn't been broken.
Thanks,
Ian.
next reply other threads:[~2016-01-21 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 11:58 Ian Campbell [this message]
2016-01-27 1:44 ` stable backport of 3 xen multiqueue network dev fixes David Miller
2016-01-27 1:44 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-01-21 11:58 Ian Campbell
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=1453377490.4320.16.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=netdev@vger.kernel.org \
--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 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.