From: Stephen Hemminger <stephen@networkplumber.org>
To: Trevor Highland <tsh@vectra.ai>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Ixgbe empty queue stats
Date: Sat, 27 Feb 2021 10:45:56 -0800 [thread overview]
Message-ID: <20210227104556.77526c43@hermes.local> (raw)
In-Reply-To: <DM5PR08MB3434A53C75B180B834951DCFA49F9@DM5PR08MB3434.namprd08.prod.outlook.com>
On Wed, 24 Feb 2021 13:24:37 +0000
Trevor Highland <tsh@vectra.ai> wrote:
> Hi all,
>
> We have a DPDK application that’s running using 82599 NICs with the ixgbe driver. Our application makes use of RSS and runs with 8 or 16 queues depending on the environment. I was reviewing xstats from a DPDK application that we run, and found that ‘rx_qN_packets’ was 0 for all queues except queue 0.
>
> I was able to reproduce this using dpdk-testpmd from the 20.11 release. Additionally I used the ethregs tool and confirmed that the registers are indeed 0. Is this expected behavior, and is there a proper way to get per queue packet counts from hardware registers?
>
> ./dpdk-testpmd -l 0-8 -n 4 -m5120,5120 -- -i --forward-mode=rxonly --rxq=2 --txq=2 --portmask=0xc --rxd=65536 --nb-cores=8 --rss-ip
>
Are you sending packets with different IP addresses?
prev parent reply other threads:[~2021-02-27 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 13:24 Trevor Highland
2021-02-27 18:45 ` Stephen Hemminger [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=20210227104556.77526c43@hermes.local \
--to=stephen@networkplumber.org \
--cc=tsh@vectra.ai \
--cc=users@dpdk.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).