From: Jakub Kicinski <kuba@kernel.org>
To: Eli Cohen <elic@nvidia.com>
Cc: virtualization <virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: utilizing multi queues of a net device
Date: Mon, 2 May 2022 09:21:34 -0700 [thread overview]
Message-ID: <20220502092134.160f43b3@kernel.org> (raw)
In-Reply-To: <DM8PR12MB5400B7E41EB88FF4C9E0F87AABC19@DM8PR12MB5400.namprd12.prod.outlook.com>
On Mon, 2 May 2022 04:29:09 +0000 Eli Cohen wrote:
> Hi all,
>
> I am experimenting with virtio net device running on a host. The net device has
> multiple queues and I am trying to measure the throughput while utilizing all
> the queues simultaneously. I am running iperf3 like this:
>
> taskset 0x1 iperf3 -c 7.7.7.24 -p 20000 & \
> taskset 0x2 iperf3 -c 7.7.7.24 -p 20001 & \
> ...
> taskset 0x80 iperf3 -c 7.7.7.24 -p 20007
>
> Server instances with matching ports exist.
>
> I was expecting traffic to be distributed over the available send queues but
> the vast majority goes to a single queue. I do see a few packets going to other
> queues.
>
> Here's what tc qdisc shows:
>
> tc qdisc show dev eth1
> qdisc mq 0: root
> qdisc fq_codel 0: parent :8 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :7 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :6 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :5 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :4 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :3 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :2 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
> qdisc fq_codel 0: parent :1 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
>
> Any idea?
Make sure XPS is configured correctly. Looks like virtio_net cooked
a less-than-prevalent-for-networking way of distributing CPUs.
next prev parent reply other threads:[~2022-05-02 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 4:29 utilizing multi queues of a net device Eli Cohen
2022-05-02 16:21 ` Jakub Kicinski [this message]
2022-05-03 10:11 ` Eli Cohen
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=20220502092134.160f43b3@kernel.org \
--to=kuba@kernel.org \
--cc=elic@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.