From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Joe Jin <joe.jin@oracle.com>, <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"David S. Miller" <davem@davemloft.net>,
Jan Beulich <JBeulich@suse.com>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH V3 0/2] limit xen vnic max queues number to online cpus number
Date: Fri, 23 Oct 2015 10:50:13 +0100 [thread overview]
Message-ID: <562A02D5.9000505@citrix.com> (raw)
In-Reply-To: <562A0108.3070501@oracle.com>
On 23/10/15 10:42, Joe Jin wrote:
> Currently xen vnic allowed to create lots of queues by set module param
> max_queues(both netback and netfront), when queues number larger than
> cpus number, it does not help for performance but need more cpu time.
>
> This patchset limit netback and netfront max queues number to online
> cpus number.
>
> Joe Jin (2):
> xen-netback: limit xen vif max queues number to online cpus
> xen-netfront: limit vnic max_queues number to online cpus
Please do not exclude the possibility for making crazy numbers of queues.
I can appreciate the want to prevent people shooting themselves in the
foot, but being able oversubscribe the number of queues is important for
performance testing.
~Andrew
prev parent reply other threads:[~2015-10-23 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 9:42 [PATCH V3 0/2] limit xen vnic max queues number to online cpus number Joe Jin
2015-10-23 9:44 ` [PATCH V3 1/2] xen-netback: limit xen vif max queues number to online cpus Joe Jin
2015-10-23 9:51 ` [Xen-devel] " Andrew Cooper
2015-10-26 14:54 ` Wei Liu
2015-10-23 9:45 ` [PATCH V3 2/2] xen-netfront: limit vnic max_queues " Joe Jin
2015-10-23 9:50 ` Andrew Cooper [this message]
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=562A02D5.9000505@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=ian.campbell@citrix.com \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).