mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Murali Krishna <muralikrishna2444b@gmail.com>
Cc: srini@kernel.org, ekansh.gupta@oss.qualcomm.com,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: misc: fastrpc: is a ctx_idr IDR -> XArray conversion wanted?
Date: Wed, 23 Sep 2026 11:28:52 +0200	[thread overview]
Message-ID: <2026092338-banking-tactics-2cfb@gregkh> (raw)
In-Reply-To: <20260923082254.15312-1-muralikrishna2444b@gmail.com>

On Wed, Sep 23, 2026 at 01:52:05PM +0530, Murali Krishna wrote:
> Hi Srini, Ekansh,
> 
> I am new to kernel development and would like to start contributing. I
> do not have much experience yet, but I am willing to learn and to put in
> the work properly.
> 
> Documentation/core-api/idr.rst states that the IDR interface is
> deprecated in favour of the XArray, and fastrpc's ctx_idr is still an
> IDR. I have a conversion prepared -- XA_FLAGS_ALLOC1, xa_alloc_cyclic()
> with the cursor kept in struct fastrpc_channel_ctx, xa_load() and
> xa_erase(), and cctx->lock left as it is -- with no intended functional
> change.
> 
> Before posting it, I would rather ask than take up your review time: is
> such a conversion wanted in fastrpc, or is the IDR usage here fine as it
> is? I have seen similar conversions in other subsystems declined as
> unnecessary, so I did not want to assume.

I doubt it's really needed unless you can prove some sort of advantage
for the change?  Is it faster on a measurable path, or less memory or
something else that would justify the churn?

idr is still a fine structure/api for many things, they don't all have
to go away, otherwise we would have done so long ago.

thanks,

greg k-h

  reply	other threads:[~2026-09-23  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  8:22 Murali Krishna
2026-09-23  9:28 ` Greg KH [this message]
2026-09-23  9:40   ` Murali Krishna
2026-09-23 10:41     ` Greg KH

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=2026092338-banking-tactics-2cfb@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muralikrishna2444b@gmail.com \
    --cc=srini@kernel.org \
    /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

all inboxes | Powered by JetHome®