Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-rdma@vger.kernel.org,
	"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
	Jack Wang <jinpu.wang@ionos.com>,
	Leon Romanovsky <leon@kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RDMA/rtrs: Use flexible array for client path stats
Date: Sun, 24 May 2026 17:22:01 -0300	[thread overview]
Message-ID: <20260524202201.GA2101751@nvidia.com> (raw)
In-Reply-To: <20260511041812.378030-1-rosenp@gmail.com>

On Sun, May 10, 2026 at 09:18:12PM -0700, Rosen Penev wrote:
> Store the client path statistics in the RTRS client path allocation
> instead of allocating them separately.
> 
> This ties the stats lifetime directly to the path and removes a separate
> allocation failure path. Keep freeing the per-CPU stats data separately,
> but do not free the embedded stats object from error paths or the stats
> kobject release handler.
> 
> Assisted-by: Codex:GPT-5.5
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> Acked-by: Jack Wang <jinpu.wang@ionos.com>
> ---
>  drivers/infiniband/ulp/rtrs/rtrs-clt-sysfs.c |  2 --
>  drivers/infiniband/ulp/rtrs/rtrs-clt.c       | 13 ++-----------
>  drivers/infiniband/ulp/rtrs/rtrs-clt.h       |  2 +-
>  3 files changed, 3 insertions(+), 14 deletions(-)

Applied to for-next

Thanks,
Jason

      parent reply	other threads:[~2026-05-24 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  4:18 [PATCH] RDMA/rtrs: Use flexible array for client path stats Rosen Penev
2026-05-12 14:39 ` Jinpu Wang
2026-05-24 20:22 ` Jason Gunthorpe [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=20260524202201.GA2101751@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=haris.iqbal@ionos.com \
    --cc=jinpu.wang@ionos.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rosenp@gmail.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