From: Leon Romanovsky <leon@kernel.org>
To: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
Shravya KN <shravya.k-n@broadcom.com>,
Saravanan Vajravel <saravanan.vajravel@broadcom.com>
Subject: Re: [PATCH rdma-next 4/9] RDMA/bnxt_re: Avoid GID level QoS update from the driver
Date: Mon, 8 Sep 2025 10:04:28 +0300 [thread overview]
Message-ID: <20250908070428.GD25881@unreal> (raw)
In-Reply-To: <20250814112555.221665-5-kalesh-anakkur.purayil@broadcom.com>
On Thu, Aug 14, 2025 at 04:55:50PM +0530, Kalesh AP wrote:
> From: Shravya KN <shravya.k-n@broadcom.com>
>
> The driver inserts a VLAN header into RoCE packets when the
> traffic was untagged by modifying the existing GID entries.
> This has caused the firmware to enforce only VLAN-based
> priority mappings, ignoring other valid priority configurations
> set via APP TLVs (e.g., DSCP selectors).
>
> Driver now has support for selecting the service level (vlan id)
> and traffic class (dscp) during modify_qp. So no need to override
> the priority update using the update gid method. Hence removing
> the code that handles the above operation.
>
> Signed-off-by: Shravya KN <shravya.k-n@broadcom.com>
> Reviewed-by: Saravanan Vajravel <saravanan.vajravel@broadcom.com>
> Reviewed-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/main.c | 94 ------------------------
> drivers/infiniband/hw/bnxt_re/qplib_sp.c | 40 ----------
> 2 files changed, 134 deletions(-)
<...>
> -
> - INIT_DELAYED_WORK(&rdev->worker, bnxt_re_worker);
> - set_bit(BNXT_RE_FLAG_QOS_WORK_REG, &rdev->flags);
You should delete worker from struct bnxt_re_dev and
BNXT_RE_FLAG_QOS_WORK_REG too.
Thanks
next prev parent reply other threads:[~2025-09-08 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 11:25 [PATCH rdma-next 0/9] bnxt_re enhancements Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 1/9] RDMA/bnxt_re: Update sysfs entries with appropriate data Kalesh AP
2025-09-08 7:03 ` Leon Romanovsky
2025-08-14 11:25 ` [PATCH rdma-next 2/9] RDMA/bnxt_re: show srq_limit in fill_res_srq_entry hook Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 3/9] RDMA/bnxt_re: RoCE Driver Dynamic Debug for HWRM's Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 4/9] RDMA/bnxt_re: Avoid GID level QoS update from the driver Kalesh AP
2025-09-08 7:04 ` Leon Romanovsky [this message]
2025-08-14 11:25 ` [PATCH rdma-next 5/9] RDMA/bnxt_re: Optimize bnxt_qplib_get_dev_attr function Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 6/9] RDMA/bnxt_re: RoCE related hardware counters update Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 7/9] RDMA/bnxt_re: Report udp source port for flow_label in bnxt_re_query_qp Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 8/9] RDMA/bnxt_re: Delete always true SGID table check Kalesh AP
2025-08-14 11:25 ` [PATCH rdma-next 9/9] RDMA/bnxt_re: Enhance a log message when bnxt_re_register_netdev fails Kalesh AP
2025-09-08 7:10 ` [PATCH rdma-next 0/9] bnxt_re enhancements Leon Romanovsky
2025-09-08 7:38 ` Kalesh Anakkur Purayil
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=20250908070428.GD25881@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=linux-rdma@vger.kernel.org \
--cc=saravanan.vajravel@broadcom.com \
--cc=selvin.xavier@broadcom.com \
--cc=shravya.k-n@broadcom.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