DPDK usage discussions
 help / color / mirror / Atom feed
From: Tony Hart <tony.hart@domainhart.com>
To: users@dpdk.org
Subject: Performance of CX7 with 'eth' pattern versus 'eth/ipv4' in hairpin
Date: Wed, 26 Jun 2024 07:39:17 -0400	[thread overview]
Message-ID: <CAC6tBwzLT+s3NjTjbCCOgVwbh_3pbWR6o7BJ4FE5c4uwP_BeGA@mail.gmail.com> (raw)

I'm using a CX7 and testing hairpin queues.  The test traffic is
entirely IPv4+UDP with distributed SIP,DIP pairs and received packets
are u-turned via hairpin in the CX7 (single 400G interface).

I see different performance when I use a pattern of 'eth' versus
'eth/ipv4' in the hairpin flow entry.  From testing it seems that
specifying just 'eth' is sufficient to invoke RSS and 'eth/ipv4'
should be equivalent since the traffic is all ipv4, but I'm getting
~104Gbps for the 'eth' pattern and  ~124Gbps for 'eth/ipv4' pattern.

Any thoughts on why there is such a performance difference here?

thanks
tony

This is the 'eth' pattern testpmd commands
flow create 0 ingress group 0 pattern end actions jump group 1 / end
flow create 0 ingress group 1 pattern eth / end actions count / rss
queues 6 7 8 9 end / end

The testpmd commands for 'eth/ipv4'
flow create 0 ingress group 0 pattern end actions jump group 1 / end
flow create 0 ingress group 1 pattern eth / ipv4 / end actions count /
rss queues 6 7 8 9 end / end


This is the testpmd command line...
dpdk-testpmd -l8-14 -a81:00.0,dv_flow_en=1 -- -i --nb-cores 6 --rxq 6
--txq 6 --port-topology loop --forward-mode=rxonly --hairpinq 4
--hairpin-mode 0x10

Versions
mlnx-ofa_kernel-24.04-OFED.24.04.0.6.6.1.rhel9u4.x86_64
kmod-mlnx-ofa_kernel-24.04-OFED.24.04.0.6.6.1.rhel9u4.x86_64
mlnx-ofa_kernel-devel-24.04-OFED.24.04.0.6.6.1.rhel9u4.x86_64
ofed-scripts-24.04-OFED.24.04.0.6.6.x86_64

DPDK: v24.03

             reply	other threads:[~2024-06-26 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 11:39 Tony Hart [this message]
2024-06-26 12:10 ` Bing Zhao
2024-06-26 13:24   ` Tony Hart
2024-06-28  9:57     ` Tony Hart

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=CAC6tBwzLT+s3NjTjbCCOgVwbh_3pbWR6o7BJ4FE5c4uwP_BeGA@mail.gmail.com \
    --to=tony.hart@domainhart.com \
    --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).