public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH qemu-server] net: increase max queues to 128
Date: Wed, 16 Nov 2022 08:37:51 +0100	[thread overview]
Message-ID: <1927f51a-1c33-0930-f515-9cc4d57cc77e@proxmox.com> (raw)
In-Reply-To: <20221116041332.810054-1-aderumier@odiso.com>

Am 16/11/2022 um 05:13 schrieb Alexandre Derumier:
> max supported queues tx + rx = 256, so 128 for combined
> https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg03917.html

do you really use such a relatively high amount of queues in practice?

The patch even mentions that on x86 one can only have 80 queue rx+tx
pairs, so maybe lets go for 64 as increased limit and wait on some
more user feedback for a even higher limit; at least if you don't need
that already in your production setups?


> 
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
>  PVE/QemuServer.pm | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 3b64089..da007f4 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -921,7 +921,7 @@ my $net_fmt = {
>      }),
>      queues => {
>  	type => 'integer',
> -	minimum => 0, maximum => 16,
> +	minimum => 0, maximum => 128,
>  	description => 'Number of packet queues to be used on the device.',
>  	optional => 1,
>      },





  reply	other threads:[~2022-11-16  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  4:13 Alexandre Derumier
2022-11-16  7:37 ` Thomas Lamprecht [this message]
2022-11-16 11:15 ` [pve-devel] applied: " Thomas Lamprecht

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=1927f51a-1c33-0930-f515-9cc4d57cc77e@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=aderumier@odiso.com \
    --cc=pve-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal