From: Danny Al-Gaaf <danny@bisect.de>
To: Sage Weil <sage@inktank.com>
Cc: Alex Elder <elder@inktank.com>,
Christian Huang <ythuang@gmail.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: limit of maximum number of rbd devices that can be mapped
Date: Fri, 02 Nov 2012 13:28:14 +0100 [thread overview]
Message-ID: <5093BC5E.10307@bisect.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1211020416410.19983@cobra.newdream.net>
Am 02.11.2012 12:22, schrieb Sage Weil:
> On Fri, 2 Nov 2012, Danny Al-Gaaf wrote:
[...]
>> Any news on this? We have seen the same issues here.
>>
>> IMO the RBD code should to something similar to some other block drivers:
>>
>> 1) reserve a major block number for RBD in general (or use the number
>> returned from the register_blkdev call, if there is no number we can
>> reserve in general for RBD, see [1])
>>
>> 2) Use this major number for all RBDs on this machine and handle each
>> new RBD via different minor numbers.
>>
>> If we can agree on this I would take a look into it and send a patch.
>
> We should probably do what SCSI does, where the minor for each device
> jumps by 16 to leave room for partitions.
That's exactly what I would propose. I wasn't sure if we really need to
leave the room for the partitions, since I'm not sure if they really
need to have contiguous numbers, but I guess there are some tools which
expect it.
> There was a thread on this a couple of weeks ago that mmy slow internet is
> preventing me from finding... :)
My internet connection isn't that slow here in Amsterdam ;-) ... but I
couldn't find another thread about this topic.
Do you remember if someone already is working on this?
Danny
prev parent reply other threads:[~2012-11-02 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 2:15 limit of maximum number of rbd devices that can be mapped Christian Huang
2012-10-18 2:18 ` Alex Elder
2012-10-18 3:12 ` Christian Huang
2012-11-02 10:59 ` Danny Al-Gaaf
2012-11-02 11:22 ` Sage Weil
2012-11-02 12:28 ` Danny Al-Gaaf [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=5093BC5E.10307@bisect.de \
--to=danny@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.com \
--cc=sage@inktank.com \
--cc=ythuang@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.