[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130327125023.159e2309@tlielax.poochiereds.net>
Date: Wed, 27 Mar 2013 12:50:23 -0400
From: Jeff Layton <jlayton@...hat.com>
To: Tejun Heo <tj@...nel.org>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
Steve Wise <swise@...ngridcomputing.com>,
Tom Tucker <tom@...ngridcomputing.com>,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH v1 2/6] amso1100: convert to using idr_alloc_cyclic
On Wed, 27 Mar 2013 09:27:55 -0700
Tejun Heo <tj@...nel.org> wrote:
> On Wed, Mar 27, 2013 at 09:18:04AM -0400, Jeff Layton wrote:
> > void c2_init_qp_table(struct c2_dev *c2dev)
> > {
> > spin_lock_init(&c2dev->qp_table.lock);
> > - idr_init(&c2dev->qp_table.idr);
> > + idr_init_cyclic(&c2dev->qp_table.idr, 0);
> > }
>
> Why is this necessary? In general, why is idr_init_cyclic()
> necessary?
>
> Thanks.
>
My thinking was that you might want to initialize the "cur" value to an
arbitrary value. All the current users though initialize it to the same
as the "start" value passed into idr_alloc_cyclic. Starting with it at
0 should be fine in all of the existing users.
I'll remove that in v2...
Thanks!
--
Jeff Layton <jlayton@...hat.com>
--
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