All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Mick <dmick@redhat.com>
To: Shinobu Kinjo <skinjo@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: MAX_RBD_IMAGES
Date: Wed, 30 Sep 2015 10:31:01 -0700	[thread overview]
Message-ID: <560C1C55.3050405@redhat.com> (raw)
In-Reply-To: <159480963.23629349.1443585524566.JavaMail.zimbra@redhat.com>

Doesn't mean anything.  It was just a medium-large number of emulated
targets.  The choice had nothing to do with the kernel.

On 09/29/2015 08:58 PM, Shinobu Kinjo wrote:
> I just want to know what that number means.
> 
> Based on the Linux kenel, that number doesn't make sense but, for the Ceph cluster, would make sense from performance, resource handling including networking resource point of views.
> 
> So, do you remember?
> 
> Shinobu
> 
> ----- Original Message -----
> From: "Dan Mick" <dmick@redhat.com>
> To: "Shinobu Kinjo" <skinjo@redhat.com>, "ceph-devel" <ceph-devel@vger.kernel.org>
> Sent: Wednesday, September 30, 2015 9:04:35 AM
> Subject: Re: [CEPH-DEVEL] MAX_RBD_IMAGES
> 
> On 09/22/2015 02:55 PM, Shinobu Kinjo wrote:
>> Hello,
>>
>> Does any of you know why *MAX_RBD_IMAGES* was changed from 16 to 128?
>> I hope that Dan remember -;
>>
>> http://resources.ustack.com/ceph/ceph/commit/2a6dcabf7f1b7550a0fa4fd223970ffc24ad7870
>>
>>  - Shinobu
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> to....have more of them?
> 


      reply	other threads:[~2015-09-30 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <737821405.20198894.1442958231356.JavaMail.zimbra@redhat.com>
2015-09-22 21:55 ` MAX_RBD_IMAGES Shinobu Kinjo
2015-09-22 22:42   ` MAX_RBD_IMAGES Josh Durgin
2015-09-22 22:53     ` MAX_RBD_IMAGES Shinobu Kinjo
2015-09-30  0:04   ` MAX_RBD_IMAGES Dan Mick
2015-09-30  3:58     ` MAX_RBD_IMAGES Shinobu Kinjo
2015-09-30 17:31       ` Dan Mick [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=560C1C55.3050405@redhat.com \
    --to=dmick@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=skinjo@redhat.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.