From: David Vrabel <david.vrabel@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Netdev <netdev@vger.kernel.org>
Cc: David Vrabel <david.vrabel@citrix.com>
Subject: Re: [Xen-devel] [PATCH net v3 2/2] xen-netfront: respect user provided max_queues
Date: Thu, 10 Sep 2015 14:35:17 +0100 [thread overview]
Message-ID: <55F18715.5000808@citrix.com> (raw)
In-Reply-To: <1441880338-4911-3-git-send-email-wei.liu2@citrix.com>
On 10/09/15 11:18, Wei Liu wrote:
> Originally that parameter was always reset to num_online_cpus during
> module initialisation, which renders it useless.
>
> The fix is to only set max_queues to num_online_cpus when user has not
> provided a value.
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
Tested-by: David Vrabel <david.vrabel@citrix.com>
David
> --- a/drivers/net/xen-netfront.c
> +++ b/drivers/net/xen-netfront.c
> @@ -2132,8 +2132,11 @@ static int __init netif_init(void)
>
> pr_info("Initialising Xen virtual ethernet driver\n");
>
> - /* Allow as many queues as there are CPUs, by default */
> - xennet_max_queues = num_online_cpus();
> + /* Allow as many queues as there are CPUs if user has not
> + * specified a value.
> + */
> + if (xennet_max_queues == 0)
> + xennet_max_queues = num_online_cpus();
>
> return xenbus_register_frontend(&netfront_driver);
> }
>
next prev parent reply other threads:[~2015-09-10 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 10:18 [PATCH net v3 0/2] xen-net{front,back}: respect user provided max_queues Wei Liu
2015-09-10 10:18 ` [PATCH net v3 1/2] xen-netback: " Wei Liu
2015-09-10 10:18 ` Wei Liu
2015-09-10 10:18 ` [PATCH net v3 2/2] xen-netfront: " Wei Liu
2015-09-10 13:35 ` David Vrabel [this message]
2015-09-10 13:35 ` David Vrabel
2015-09-10 10:18 ` Wei Liu
2015-09-10 17:12 ` [PATCH net v3 0/2] xen-net{front,back}: " David Miller
2015-09-10 17:12 ` [PATCH net v3 0/2] xen-net{front, back}: " David Miller
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=55F18715.5000808@citrix.com \
--to=david.vrabel@citrix.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 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.