All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vangelis Tasoulas <vangelis-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
To: Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Extend LID space in InfiniBand beyond 48k? Is this really possible?
Date: Wed, 29 Mar 2017 18:07:47 +0200	[thread overview]
Message-ID: <b9531f99-c350-3985-edae-296b1bc97509@simula.no> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]

Hello,

I was reading a year+ old article where Steve Scott (CRAY CTO) was
interviewed here:
https://www.nextplatform.com/2016/01/08/cray-cto-connects-the-dots-on-future-interconnects/

At a certain point Steve mentions (or at least that's what the article
claims):

/InfiniBand has another limit in terms of the number of logical IDs, or
LIDs, it can support, which is around 48,000 end points, and for the
most point, people have stayed within that limit. There is an extended
version that has some higher packet overhead that can go to higher
scalability./

Is this true? Is there any reference that one can point me to for the
part of the "extended version that has some higher packet overhead that
can go to higher scalability"?

To the best of my knowledge, there is no extended version defined in the
InfiniBand specification. What is mentioned is that /The unicast LID
range is a flat identifier space defined as 0x0001 to 0xBFFF./

Vangelis


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2017-03-29 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 16:07 Vangelis Tasoulas [this message]
     [not found] ` <b9531f99-c350-3985-edae-296b1bc97509-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
2017-03-30  4:04   ` Extend LID space in InfiniBand beyond 48k? Is this really possible? Leon Romanovsky
     [not found]     ` <20170330040409.GL20443-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-03-31  4:25       ` Hefty, Sean

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=b9531f99-c350-3985-edae-296b1bc97509@simula.no \
    --to=vangelis-s8y2klwgcofhl2p70bpvqq@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 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.