DPDK usage discussions
 help / color / mirror / Atom feed
From: Tony Hart <tony.hart@domainhart.com>
To: users@dpdk.org
Subject: Re: Performance of CX7 with 3 flow groups versus 2
Date: Sat, 29 Jun 2024 14:42:21 -0400	[thread overview]
Message-ID: <CAC6tBwz3Drx6w8qWXEJHMGCigK3qivKRNqMQnqsst-kqROmuDg@mail.gmail.com> (raw)
In-Reply-To: <CAC6tBwxS3qn43oQjmCAwHdL35V7qNa64q8e=oz97=5P+7svBAA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]

I didn't mention that the packet size used for the tests was 68 Bytes.

Also note there is a typo in the profile setting, the PIR rate used was
1200000000 (not 150000000).  However this does not seem to make any
difference to the results.

On Fri, Jun 28, 2024 at 5:53 AM Tony Hart <tony.hart@domainhart.com> wrote:

> I'm seeing an unexpected performance drop on the CX7 when using 3 groups
> (with a policer) versus 3 groups (without policer) versus (2 groups without
> policer).  The performance of each configuration is  72 Gbps, 104 Gbps and
> 124 Gbps respectively.   So the first configuration drops to almost half
> the performance of the third even though all 3 are just hairpinning packets
> (the policier is used to color the packet only, no fate actions are taken
> as a result).
>
> This is on a 400G link and using SWS mode.  I know there was a similar
> issue reported on this mailing list recently related to SWS versus HWS
> performance, but this issue seems different.
>
> Any thoughts welcome.
>
> thanks
> tony
>
> These are the testpmd commands used to recreate the issue...
>
>
> *Common commands:*add port meter profile trtcm_rfc4115 0 1 1000 150000000
> 1000 1000 1
>
> add port meter policy 0 1 g_actions end y_actions end r_actions drop  / end
>
> create port meter 0 1 1 1 yes 0xffff 0 g 0
>
>
>
> *3 groups with policer*
> flow create 0 ingress group 0 pattern end actions jump group 1 / end
>
> flow create 0 ingress group 1 pattern end actions meter mtr_id 1 / jump
> group 2 / end
>
> flow create 0 ingress group 2 pattern eth / ipv4 / end actions count / rss
> queues 6 7 8 9 end / end
>
>
>
> *3 groups without policer*
> flow create 0 ingress group 0 pattern end actions jump group 1 / end
>
> flow create 0 ingress group 1 pattern end actions jump group 2 / end
>
> flow create 0 ingress group 2 pattern eth / ipv4 / end actions count / rss
> queues 6 7 8 9 end / end
>
>
>
> *2 groups without policer*
> 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
>
> thanks,
> tony
>
> *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
>
>

-- 
tony

[-- Attachment #2: Type: text/html, Size: 3277 bytes --]

      reply	other threads:[~2024-06-29 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  9:53 Tony Hart
2024-06-29 18:42 ` Tony Hart [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=CAC6tBwz3Drx6w8qWXEJHMGCigK3qivKRNqMQnqsst-kqROmuDg@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).