[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4C9B3E15.5080002@gmail.com>
Date: Thu, 23 Sep 2010 13:46:29 +0200
From: Tejun Heo <htejun@...il.com>
To: Paul Mundt <lethal@...ux-sh.org>
CC: Roland Dreier <rdreier@...co.com>,
Ohad Ben-Cohen <ohad@...ery.com>, linux-kernel@...r.kernel.org,
"Jean Delvare (PC drivers, core)" <khali@...ux-fr.org>,
"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
Roland Dreier <rolandd@...co.com>,
Sean Hefty <sean.hefty@...el.com>,
Hal Rosenstock <hal.rosenstock@...il.com>,
Steve Wise <swise@...lsio.com>, Neil Brown <neilb@...e.de>,
Paul Mackerras <paulus@...ba.org>, linux-i2c@...r.kernel.org,
linux-rdma@...r.kernel.org, dm-devel@...hat.com,
linux-raid@...r.kernel.org, linux-ppp@...r.kernel.org,
netdev@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Alasdair G Kergon <agk@...hat.com>
Subject: Re: idr_get_new_exact ?
Hello,
On 09/23/2010 01:42 PM, Paul Mundt wrote:
> On Mon, Sep 20, 2010 at 11:26:47PM +0200, Tejun Heo wrote:
>> Hello,
>>
>> On 09/20/2010 10:35 PM, Roland Dreier wrote:
>>> Looks fine to me as an improvement over the status quo, but I wonder how
>>> many of these places could use the radix_tree stuff instead? If you're
>>> not using the ability of the idr code to assign an id for you, then it
>>> seems the radix_tree API is a better fit.
>>
>> I agree. Wouldn't those users better off simply using radix tree?
>>
> It could go either way. I was about to write the same function when
> playing with it for IRQ mapping, the idea being to propagate the initial
> tree with sparse static vectors and then switch over to dynamic IDs for
> virtual IRQ creation. I ended up going with a radix tree for other
> reasons, though.
I see. If there are use cases where fixed and dynamic IDs need to be
mixed, no objection from me.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists