From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
netdev@vger.kernel.org
Cc: boris.ostrovsky@oracle.com, wei.liu2@citrix.com,
paul.durrant@citrix.com, Juergen Gross <jgross@suse.com>
Subject: [PATCH 0/2] xen/net: limit number of tx/rx queues
Date: Tue, 10 Jan 2017 14:32:50 +0100 [thread overview]
Message-ID: <20170110133252.5346-1-jgross@suse.com> (raw)
The Xen network frontend/backend supports multiple tx/rx queues for one
virtual interface. The number of queues supported by the backend is
set to the number of cpus of the backend driver domain (usually dom0)
and the number of queues requested by the frontend is limited by the
number of vcpus of the related guest.
On large systems this can lead to ridiculous large number of queues
exhausting the required number of grant pages rather quick.
To avoid this limit the default maximum on both sides to 8. Both
frontend and backend maximum can be individually tuned via module
parameters.
Juergen Gross (2):
xen/netfront: set default upper limit of tx/rx queues to 8
xen/netback: set default upper limit of tx/rx queues to 8
drivers/net/xen-netback/netback.c | 6 ++++--
drivers/net/xen-netfront.c | 6 ++++--
2 files changed, 8 insertions(+), 4 deletions(-)
--
2.10.2
next reply other threads:[~2017-01-10 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 13:32 Juergen Gross [this message]
2017-01-10 13:32 ` [PATCH 1/2] xen/netfront: set default upper limit of tx/rx queues to 8 Juergen Gross
2017-01-10 14:53 ` Boris Ostrovsky
2017-01-10 14:53 ` Boris Ostrovsky
2017-01-10 15:02 ` Juergen Gross
2017-01-10 15:02 ` Juergen Gross
2017-01-10 13:32 ` Juergen Gross
2017-01-10 13:32 ` [PATCH 2/2] xen/netback: " Juergen Gross
2017-01-10 13:32 ` Juergen Gross
2017-01-10 13:54 ` [PATCH 0/2] xen/net: limit number of tx/rx queues Wei Liu
2017-01-10 13:54 ` Wei Liu
2017-01-30 2:55 ` Boris Ostrovsky
2017-01-30 2:55 ` Boris Ostrovsky
2017-01-10 13:32 Juergen Gross
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=20170110133252.5346-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=wei.liu2@citrix.com \
--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.