public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-rdma@vger.kernel.org, justin.chen@hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: infiniband limit of 32 cards per system?
Date: Mon, 25 Jan 2010 20:59:06 -0700	[thread overview]
Message-ID: <20100126035906.GA23347@ldl.fc.hp.com> (raw)
In-Reply-To: <adaiqapplv7.fsf@roland-alpha.cisco.com>

* Roland Dreier <rdreier@cisco.com>:
> 
>  > My colleague points out the following enum in uverbs_main.c:
>  > 
>  > 	enum {
>  > 		IB_UVERBS_MAJOR       = 231,
>  > 		IB_UVERBS_BASE_MINOR  = 192,
>  > 		IB_UVERBS_MAX_DEVICES = 32
>  > 	};
>  > 
>  > Experimentally, we've determined that on a system where we
>  > plugged in 40 IB cards, OFED only reports 32 cards are present.
> 
> wow, 40 HCAs in one system !

HP sell some pretty big systems. :)

>  > If that enum is indeed the limiting factor, would someone mind
>  > explaining (or pointing me at TFM ;) why it's limited to 32
>  > devices?
> 
> That dates back to when device #s had 8 bits for major and 8 bits for
> minor.  We got one major assigned for IB, and had to split up the 256
> minors that gave us among userspace verbs, management access, etc.  And
> 32 seemed like a pretty reasonable limit for most uses.

Thanks for the explanation.

> Nowadays I guess we should look into expanding that to dynamic device
> numbers on overflow, assuming you do have a realistic situation where
> someone would want to use that many adapters per system.

Think of a large scale-up ia64 box, possibly running some
virtualization stack.

I'm guessing that it's not just a simple kernel fix though since
OFED has to change too, right?

/ac

  reply	other threads:[~2010-01-26  3:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 23:50 infiniband limit of 32 cards per system? Alex Chiang
     [not found] ` <20100125235013.GD2828-TYHnb5JFxdjwUeR5qC7q4g@public.gmane.org>
2010-01-26  3:48   ` Roland Dreier
2010-01-26  3:59     ` Alex Chiang [this message]
     [not found]       ` <20100126035906.GA23347-e+Ta4ugHZmL3oGB3hsPCZA@public.gmane.org>
2010-01-26  4:03         ` Roland Dreier
     [not found]           ` <adaaaw1pl5d.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-26 21:38             ` Alex Chiang
     [not found]               ` <20100126213803.GA12035-e+Ta4ugHZmL3oGB3hsPCZA@public.gmane.org>
2010-01-26 23:52                 ` Roland Dreier
     [not found]     ` <adaiqapplv7.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-26 22:03       ` Alex Chiang
2010-01-27  0:09         ` Roland Dreier

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=20100126035906.GA23347@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=justin.chen@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rdreier@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox