From: Leon Romanovsky <leon@kernel.org>
To: Patrisious Haddad <phaddad@nvidia.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH rdma-next 0/5] Add optional-counters binding support
Date: Mon, 10 Mar 2025 09:54:15 +0200 [thread overview]
Message-ID: <20250310075415.GA505188@unreal> (raw)
In-Reply-To: <174146229393.310407.731855525292951254.b4-ty@kernel.org>
On Sat, Mar 08, 2025 at 02:31:33PM -0500, Leon Romanovsky wrote:
>
> On Tue, 04 Mar 2025 16:15:24 +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.com>
> >
> > From Patrisious,
> >
> > Add optional-counters binding support together with new packets/bytes
> > counters. Previously optional-counters were on a per link basis, this
> > series allows users to bind optional-counters to a specific counter,
> > which allows tracking optional-counter over a specific QP group.
> >
> > [...]
>
> Applied, thanks!
>
> [1/5] RDMA/mlx5: Add optional counters for RDMA_TX/RX_packets/bytes
> https://git.kernel.org/rdma/rdma/c/30c77a88e3ffe9
> [2/5] RDMA/core: Create and destroy rdma_counter using rdma_zalloc_drv_obj()
> https://git.kernel.org/rdma/rdma/c/3644e21c005fcf
> [3/5] RDMA/core: Add support to optional-counters binding configuration
> https://git.kernel.org/rdma/rdma/c/df5f4ff6319a6f
> [4/5] RDMA/core: Pass port to counter bind/unbind operations
> https://git.kernel.org/rdma/rdma/c/d73531da19eb56
> [5/5] RDMA/mlx5: Support optional-counters binding for QPs
> https://git.kernel.org/rdma/rdma/c/7bcd537adb21b5a
Unfortunately, but I need to drop this series from our wip branches.
The reason to it is patch #5 which has layer violation of bringing
RDMA counters logic into flow steering code.
As such it caused to multiple kbuild errors, because fs.c is available
only when CONFIG_INFINIBAND_USER_ACCESS is set, while counters and
rdmatool (bind/unbind logic) is not limited to user space verbs only.
This series needs to be fixed:
1. RDMA counters logic need to stay in counter.c
2. Optional counters need to work on all type of QPs.
Thanks
>
> Best regards,
> --
> Leon Romanovsky <leon@kernel.org>
>
prev parent reply other threads:[~2025-03-10 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 14:15 [PATCH rdma-next 0/5] Add optional-counters binding support Leon Romanovsky
2025-03-04 14:15 ` [PATCH mlx5-next 1/5] RDMA/mlx5: Add optional counters for RDMA_TX/RX_packets/bytes Leon Romanovsky
2025-03-04 14:15 ` [PATCH rdma-next 2/5] RDMA/core: Create and destroy rdma_counter using rdma_zalloc_drv_obj() Leon Romanovsky
2025-03-04 14:15 ` [PATCH rdma-next 3/5] RDMA/core: Add support to optional-counters binding configuration Leon Romanovsky
2025-03-04 14:15 ` [PATCH rdma-next 4/5] RDMA/core: Pass port to counter bind/unbind operations Leon Romanovsky
2025-03-04 14:15 ` [PATCH mlx5-next 5/5] RDMA/mlx5: Support optional-counters binding for QPs Leon Romanovsky
2025-03-08 19:31 ` [PATCH rdma-next 0/5] Add optional-counters binding support Leon Romanovsky
2025-03-10 7:54 ` Leon Romanovsky [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=20250310075415.GA505188@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=phaddad@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.