linux-kernel - Re: infiniband limit of 32 cards per system?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100126213803.GA12035@ldl.fc.hp.com>
Date:	Tue, 26 Jan 2010 14:38:03 -0700
From:	Alex Chiang <achiang@...com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	linux-rdma@...r.kernel.org, justin.chen@...com,
	linux-kernel@...r.kernel.org
Subject: Re: infiniband limit of 32 cards per system?

* Roland Dreier <rdreier@...co.com>:
> 
>  > 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.

Ok.

> 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).

I take it this concern is what prevents us from simply increasing
IB_UVERBS_MAX_DEVICES to 64 or something?

thanks,
/ac
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/