From: Raslan Darawsheh <rasland@nvidia.com>
To: "Minggang(Gavin) Li" <gavinl@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>
Subject: RE: [PATCH V1] net/mlx5: store IPv6 TC detection result in physical device
Date: Sun, 25 Feb 2024 14:45:37 +0000 [thread overview]
Message-ID: <MN0PR12MB605663527C9D387150C5764ACF5B2@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240130064913.1916709-1-gavinl@nvidia.com>
Hi,
> -----Original Message-----
> From: Gavin Li <gavinl@nvidia.com>
> Sent: Tuesday, January 30, 2024 8:49 AM
> To: Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Jiawei(Jonny)
> Wang <jiaweiw@nvidia.com>
> Subject: [PATCH V1] net/mlx5: store IPv6 TC detection result in physical device
>
> Previously, discovering of IPv6 traffic class would happen on each device not
> sharing context with others. However, It's not necessary to repeat it on
> devices of the same physical device. A flow will be created and destroyed in
> the detection, which may trigger cache allocation and take more memory in
> scale cases.
>
> To solve the problem, store the discovering of IPv6 traffic class result in
> physical device, and do it only once per physical device.
>
> Fixes: 569b8340a012 ("net/mlx5: discover IPv6 traffic class support in RDMA
> core")
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
> Acked-by: Suanming Mou <suanmingm@nvidia.com>
Patch applied to next-net-mlx
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2024-02-25 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 6:49 Gavin Li
2024-02-25 14:45 ` 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=MN0PR12MB605663527C9D387150C5764ACF5B2@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=jiaweiw@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@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).