From: Raslan Darawsheh <rasland@nvidia.com>
To: Suanming Mou <suanmingm@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: limit implicitly MPLS RSS expansion
Date: Wed, 28 Jul 2021 13:57:12 +0000 [thread overview]
Message-ID: <DM4PR12MB50549F5D59FB90DB6CBA3C4ECFEA9@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210728082410.12234-1-suanmingm@nvidia.com>
Hi,
> -----Original Message-----
> From: Suanming Mou <suanmingm@nvidia.com>
> Sent: Wednesday, July 28, 2021 11:24 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: Raslan Darawsheh <rasland@nvidia.com>; dev@dpdk.org
> Subject: [PATCH] net/mlx5: limit implicitly MPLS RSS expansion
>
> As [1] optimized the MPLS RSS expansion before, this commit limits
> the implicitly MPLS RSS expansion for MPLSoGRE as well. For the
> RSS flow matcher to GRE level only, it will not expand the MPLS
> match item for the sub flows due to performance consideration.
>
> The original RSS flow match item:
> ETH VLAN IPV6 GRE GRE_KEY END
>
> The previous RSS expansion:
> ETH VLAN IPV6 GRE GRE_KEY END
> ETH VLAN IPV6 GRE GRE_KEY IPV4 END
> ETH VLAN IPV6 GRE GRE_KEY MPLS IPV4 END
> ETH VLAN IPV6 GRE GRE_KEY MPLS ETH IPV4 END
>
> New RSS expansion:
> ETH VLAN IPV6 GRE GRE_KEY END
> ETH VLAN IPV6 GRE GRE_KEY IPV4 END
>
> [1]
> commit a26cc30fa046 ("net/mlx5: limit inner RSS expansion for MPLS")
>
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> Acked-by: Xiaoyu Min <jackmin@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-07-28 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 8:24 Suanming Mou
2021-07-28 13:57 ` Raslan Darawsheh [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=DM4PR12MB50549F5D59FB90DB6CBA3C4ECFEA9@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
/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).