Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Bernard Metzler <bernard.metzler@linux.dev>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: rosenp@gmail.com, leon@kernel.org, kees@kernel.org,
	gustavoars@kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [RFC PATCH] RDMA/siw: use kzalloc_flex
Date: Wed, 29 Apr 2026 18:04:15 +0200	[thread overview]
Message-ID: <58485c92-0ee5-4927-b9e4-dd4858219b17@linux.dev> (raw)
In-Reply-To: <20260428155536.GA2774550@nvidia.com>

On 28.04.2026 17:55, Jason Gunthorpe wrote:
> On Tue, Apr 21, 2026 at 09:28:21PM +0200, bernard.metzler@linux.dev wrote:
>> From: Bernard Metzler <bernard.metzler@linux.dev>
>>
>> Simplify umem allocation by using flexible array member.
>> Add __counted_by to get extra runtime analysis.
>>
>> Suggested-by: Rosen Penev <rosenp@gmail.com>
>> Signed-off-by: Bernard Metzler <bernard.metzler@linux.dev>
>> ---
>>   drivers/infiniband/sw/siw/siw.h     |  4 ++--
>>   drivers/infiniband/sw/siw/siw_mem.c | 19 ++++++-------------
>>   drivers/infiniband/sw/siw/siw_mem.h |  2 +-
>>   3 files changed, 9 insertions(+), 16 deletions(-)
> 
> Sashiko has quite a few interesting things to say about this:
> 
> https://sashiko.dev/#/patchset/20260421192821.2305-1-bernard.metzler%40linux.dev
> 
> Jason
Excellent. I thought about that issue, but probably my
conclusion that's all right is just wrong.
I'll rework.

Thanks,
Bernard.

      reply	other threads:[~2026-04-29 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 19:28 [RFC PATCH] RDMA/siw: use kzalloc_flex bernard.metzler
2026-04-21 21:32 ` Rosen Penev
2026-04-28 15:55 ` Jason Gunthorpe
2026-04-29 16:04   ` Bernard Metzler [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=58485c92-0ee5-4927-b9e4-dd4858219b17@linux.dev \
    --to=bernard.metzler@linux.dev \
    --cc=gustavoars@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=kees@kernel.org \
    --cc=leon@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