From: Danny Al-Gaaf <danny@bisect.de>
To: Alex Elder <elder@inktank.com>
Cc: 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 11:59:25 +0100 [thread overview]
Message-ID: <5093A78D.4060409@bisect.de> (raw)
In-Reply-To: <507F66F1.4000509@inktank.com>
Am 18.10.2012 04:18, schrieb Alex Elder:
> On 10/17/2012 09:15 PM, Christian Huang wrote:
>> Hi,
>> what is the maximum number of rbd devices that can be mapped on a
>> single host?
>> we recently did a test to mount a large number of rbd devices and
>> hit a wall around 230
>> with the following message
>
> That sounds about right. We were just discussing this earlier
> this week. It's limited at the moment by the number of major
> device numbers available on the system, and I think you found
> that limit. We would obviously like to have a solution for
> this but we've only just started considering options.
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.
Regards
Danny
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=Documentation/devices.txt;hb=HEAD
next prev parent reply other threads:[~2012-11-02 10:59 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 [this message]
2012-11-02 11:22 ` Sage Weil
2012-11-02 12:28 ` Danny Al-Gaaf
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=5093A78D.4060409@bisect.de \
--to=danny@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@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.