public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Alex Chiang <achiang-VXdhtT5mjnY@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	justin.chen-VXdhtT5mjnY@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: infiniband limit of 32 cards per system?
Date: Mon, 25 Jan 2010 20:03:58 -0800	[thread overview]
Message-ID: <adaaaw1pl5d.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <20100126035906.GA23347-e+Ta4ugHZmL3oGB3hsPCZA@public.gmane.org> (Alex Chiang's message of "Mon, 25 Jan 2010 20:59:06 -0700")


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

Dunno about OFED.  Nothing sane is hard-coding major/minor numbers
though -- so I think OFED should be OK, asuming there are no crazy
scripts that bypass udev creating device nodes etc.

I don't think that it's _totally_ trivial in the kernel -- we do need to
add some code in several places to allocate dynamic device numbers when
we run out of the static allocation (probably best to keep the legacy
device numbers for "small" < 32 adapter systems, since there may be
really small systems with static hard-coded /dev etc).

 - R.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-01-26  4:03 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
     [not found]       ` <20100126035906.GA23347-e+Ta4ugHZmL3oGB3hsPCZA@public.gmane.org>
2010-01-26  4:03         ` Roland Dreier [this message]
     [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=adaaaw1pl5d.fsf@roland-alpha.cisco.com \
    --to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=achiang-VXdhtT5mjnY@public.gmane.org \
    --cc=justin.chen-VXdhtT5mjnY@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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