DPDK usage discussions
 help / color / mirror / Atom feed
From: Pavel Vazharov <freakpv@gmail.com>
To: "Ruslan R. Laishev" <zator@yandex.ru>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: RSS on 82599ES/X520-2
Date: Fri, 10 Feb 2023 15:18:26 +0200	[thread overview]
Message-ID: <CAK9EM1_f2YFEDjJYh_A=Nn+neqWtA7siE8rjdcP8gfTKC0xJsQ@mail.gmail.com> (raw)
In-Reply-To: <484931676028579@mail.yandex.ru>

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

Hi,

I'm almost sure 82599ES doesn't support RSS with the L4 protocols (TCP,
UDP, etc). As far as I remember I hit this issue about a year ago.

What is the value of `dev_info.flow_type_rss_offloads` obtained like:

rte_eth_dev_info dev_info;
rte_eth_dev_info_get(nic_port_id, &dev_info);


The `flow_type_rss_offloads` contains the supported RSS flags by the device.

On Fri, Feb 10, 2023 at 3:10 PM Ruslan R. Laishev <zator@yandex.ru> wrote:

> Hello!
>
> I have tried to use RSS, I do the same piece of code on NXP ls2160 and on
> Intel with the 82599ES, on NXP I see that incoming traffic is distributed
> across queues.
> On Intel I see that all incoming packet still in the queue #0.
> So, what I'm need to check additionally (at initialization/setup time)   ?
>
> Thanks-in-advance.
>
>
>
> 10-02-2023 15:17:24.718 128431 [CGWPROC\tootoo2_cgw_start:1373]
> %TTR2CGW-I:  3---TTR3 [Device:0000:02:00.1, _PEA03:, WAN] --- modified RSS
> hash function based on hardware support,requested:0x3bffc configured:0x38d34
>
> Translated bits for readability:
> 10-02-2023 15:17:24.718 128431 [CGWPROC\tootoo2_cgw_start:1383]
> RSS Offloads:
> RTE_ETH_RSS_IPV4|RTE_ETH_RSS_NONFRAG_IPV4_TCP|RTE_ETH_RSS_NONFRAG_IPV4_UDP|RTE_ETH_RSS_IPV6|RTE_ETH_RSS_NONFRAG_IPV6_TCP|RTE_ETH_RSS_NONFRAG_IPV6_UDP|RTE_ETH_RSS_IPV6_EX|RTE_ETH_RSS_IPV6_TCP_EX|RTE_ETH_RSS_IPV6_UDP_EX
>
> Test IP traffic is generated by IPERF3 (TCP). Counters from *struct* rte_eth_stats
> follows:
>
> at NXP lx216010-02-2023; 15:19:18; dpni.2; _PEA01:; 1---PUZZLE; LAN;
> 272194; 8086631; 18122106; 12242301932; 0; 0; 0; 0
> q0[33929; 1446431; 0; 0; 0];
> q1[46998; 1328423; 0; 0; 0];
> q2[28776; 1623997; 0; 0; 0];
> q3[41012; 1195463; 0; 0; 0];
> q4[23007; 427604; 0; 0; 0];
> q5[35160; 1150040; 0; 0; 0];
> q6[16089; 760039; 0; 0; 0];
> q7[47240; 154326; 0; 0; 0];
>
> on Intel with 82599ES/520-2
> 10-02-2023; 15:19:44; 0000:02:00.0; _PEA02:; 4---PUZZLE; LAN; 8122102;
> 442634; 12296494642; 29295238; 0; 0; 0; 0
> q0[8122102; 442635; 12296494642; 29295286; 0];
> q1[0; 0; 0; 0; 0];
> q2[0; 0; 0; 0; 0];
> q3[0; 0; 0; 0; 0];
> q4[0; 0; 0; 0; 0];
> q5[0; 0; 0; 0; 0];
> q6[0; 0; 0; 0; 0];
> q7[0; 0; 0; 0; 0];
>
>
>
>
>
> ---
> С уважением,
> Ruslan R. Laishev
> OpenVMS bigot, natural born system/network progger, C contractor.
> +79013163222
> +79910009922
>
>

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

  reply	other threads:[~2023-02-10 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 13:10 Ruslan R. Laishev
2023-02-10 13:18 ` Pavel Vazharov [this message]
2023-02-10 20:15   ` Ruslan R. Laishev

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='CAK9EM1_f2YFEDjJYh_A=Nn+neqWtA7siE8rjdcP8gfTKC0xJsQ@mail.gmail.com' \
    --to=freakpv@gmail.com \
    --cc=users@dpdk.org \
    --cc=zator@yandex.ru \
    /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).