From: Andrew Morton <akpm@osdl.org>
To: Kevin Corry <kevcorry@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
torvalds@osdl.org, agk@redhat.com,
Jim Houston <jim.houston@comcast.net>
Subject: Re: [PATCH] 1/1: Device-Mapper: Remove 1024 devices limitation
Date: Fri, 2 Jul 2004 12:42:18 -0700 [thread overview]
Message-ID: <20040702124218.0ad27a85.akpm@osdl.org> (raw)
In-Reply-To: <200407021233.09610.kevcorry@us.ibm.com>
Kevin Corry <kevcorry@us.ibm.com> wrote:
>
> > Yes, idr is the one to use. That linear search you have in there becomes
> > logarithmic. Will speed up the registration of 100,000 minors no end ;)
>
> I've got a patch that switches from a bit-set to an IDR structure. The only
> thing I'm slightly uncertain about is the case where we're trying to create
> a device with a specific minor number (when creating a DM device, you have
> the choice to specify a minor number or have DM find the first available
> one). To do this, I call idr_find() with the desired minor. If that returns
> NULL (meaning it's not already in use), then I call idr_get_new_above() with
> that same desired minor. In the cases I've tested, this always chooses the
> desired minor, but can we depend on that behavior?
Yes, that has to work - you're holding the lock throughout.
It would be sensible to make that a part of the idr API though.
next prev parent reply other threads:[~2004-07-02 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 15:35 Kevin Corry
2004-07-01 21:38 ` Andrew Morton
2004-07-02 2:54 ` Kevin Corry
2004-07-02 3:30 ` Andrew Morton
2004-07-02 17:33 ` Kevin Corry
2004-07-02 19:42 ` Andrew Morton [this message]
2004-07-06 18:23 ` Kevin Corry
2004-07-06 21:23 ` Andrew Morton
2004-07-06 21:35 ` Alasdair G Kergon
2004-07-06 22:04 ` Alasdair G Kergon
2004-07-06 22:20 ` Andrew Morton
2004-07-06 22:07 ` Jim Houston
2004-07-06 22:28 ` Andrew Morton
2004-07-06 23:00 ` Jim Houston
2004-07-06 23:16 ` Andrew Morton
2004-07-07 10:58 ` Jim Houston
2004-07-07 11:10 ` Andrew Morton
2004-07-12 14:49 ` Kevin Corry
2004-07-12 18:14 ` Andrew Morton
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=20040702124218.0ad27a85.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jim.houston@comcast.net \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®