From: Gerry Wan <gerryw@stanford.edu>
To: Asaf Penso <asafp@nvidia.com>
Cc: "users@dpdk.org" <users@dpdk.org>, Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-users] RSS with VLAN tagged packets
Date: Sat, 24 Oct 2020 23:00:57 -0700 [thread overview]
Message-ID: <CAAcwi38gSwFimGX5q+sA73B0VQXe1SAmcE2qV_zYw0jo-RUTPA@mail.gmail.com> (raw)
In-Reply-To: <DM5PR12MB240689C3BCED8AC9F0637B1BCD180@DM5PR12MB2406.namprd12.prod.outlook.com>
I am using DPDK v20.08
On Sat, Oct 24, 2020 at 10:56 PM Asaf Penso <asafp@nvidia.com> wrote:
> Hello Gerry,
>
> Thanks for your email.
>
> What version of DPDK are you using?
>
> We are familiar with this issue in our mlx5 pmd in the latest code and are
> working on a fix.
>
> Will let you know as soon as we have it.
>
> Thanks,
> Asaf Penso
>
> Regards,
> Asaf Penso
>
>
> ------------------------------
> *From:* users <users-bounces@dpdk.org> on behalf of Gerry Wan <
> gerryw@stanford.edu>
> *Sent:* Sunday, October 25, 2020, 00:05
> *To:* users@dpdk.org
> *Subject:* [dpdk-users] RSS with VLAN tagged packets
>
> Hello,
>
> I am configuring RSS through through rte_eth_dev_configure using
> rte_eth_conf with mq_ mode = ETH_MQ_RSS and specifying rss_hf = ETH_RSS_IP
> | ETH_RSS_TCP | ETH_RSS_UDP. I've noticed that even single VLAN tagged
> packets do not get hashed.
>
> Is there a flag I am missing to do this? Is RSS possible on tagged packets?
>
> I am using a connectx-5 with the mlx5 PMD
>
> Thanks,
>
>
next prev parent reply other threads:[~2020-10-25 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 21:04 Gerry Wan
2020-10-25 5:56 ` Asaf Penso
2020-10-25 6:00 ` Gerry Wan [this message]
2020-10-25 15:35 ` Alireza Sanaee
2020-10-25 17:58 ` Matan Azrad
2020-10-25 19:14 ` Gerry Wan
2020-10-25 19:57 ` Matan Azrad
2020-10-26 7:29 ` Gerry Wan
2020-10-26 7:33 ` Matan Azrad
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=CAAcwi38gSwFimGX5q+sA73B0VQXe1SAmcE2qV_zYw0jo-RUTPA@mail.gmail.com \
--to=gerryw@stanford.edu \
--cc=asafp@nvidia.com \
--cc=matan@nvidia.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).