public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Vangelis Tasoulas <vangelis-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
Cc: Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Extend LID space in InfiniBand beyond 48k? Is this really possible?
Date: Thu, 30 Mar 2017 07:04:09 +0300	[thread overview]
Message-ID: <20170330040409.GL20443@mtr-leonro.local> (raw)
In-Reply-To: <b9531f99-c350-3985-edae-296b1bc97509-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Wed, Mar 29, 2017 at 06:07:47PM +0200, Vangelis Tasoulas wrote:
> 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./

Right, there is no any extended version of that spec.
As far as I know, Intel's OmniPath technology is marketed as new and
extended version of Infiniband [1], so it is probably that he referenced to it.

[1] http://www.intel.com/content/www/us/en/high-performance-computing-fabrics/omni-path-architecture-fabric-overview.html

>
> Vangelis
>




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-03-30  4:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 16:07 Extend LID space in InfiniBand beyond 48k? Is this really possible? Vangelis Tasoulas
     [not found] ` <b9531f99-c350-3985-edae-296b1bc97509-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
2017-03-30  4:04   ` Leon Romanovsky [this message]
     [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=20170330040409.GL20443@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vangelis-S8y2klWGCOFhl2p70BpVqQ@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