public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jacob Moroni <jmoroni@google.com>
Cc: "Czurylo, Krzysztof" <krzysztof.czurylo@intel.com>,
	"Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>,
	"leon@kernel.org" <leon@kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH rdma-next] RDMA/irdma: Convert QP table to xarray
Date: Tue, 20 Jan 2026 14:58:30 -0400	[thread overview]
Message-ID: <20260120185830.GV961572@ziepe.ca> (raw)
In-Reply-To: <CAHYDg1QRh5dGd6B5C0N96PNkXzKguTNggQzFcbaw6PtCAPVTQQ@mail.gmail.com>

On Mon, Jan 19, 2026 at 10:56:26AM -0500, Jacob Moroni wrote:

> > Finally, the xarray was intended to replace radix tree. This is not
> > a vector-like (dynamically resized array) data structure.
> > Not sure if this is the right application for it.

xarray is an appropriate data structure for any kind of dynamic array
that has good clustering of values. Probably matches this well.
 
> It's just really easy to drop in place of the existing array for cases like this
> where the array is being used as an ID->pointer map and the IDs need
> to remain consistent for the object. It seems to be the go-to for many RDMA
> drivers.

I would certainly expect drivers to use xarray instead of allocating
their max possible ID tracking spaces.

That said someone from intel needs to ack this..

Jason

      reply	other threads:[~2026-01-20 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18  1:25 [PATCH rdma-next] RDMA/irdma: Convert QP table to xarray Jacob Moroni
2026-01-19 12:53 ` Czurylo, Krzysztof
2026-01-19 15:56   ` Jacob Moroni
2026-01-20 18:58     ` 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=20260120185830.GV961572@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=jmoroni@google.com \
    --cc=krzysztof.czurylo@intel.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tatyana.e.nikolova@intel.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