From: Vangelis Tasoulas <vangelis-S8y2klWGCOFhl2p70BpVqQ@public.gmane.org>
To: Linux RDMA Mailing List
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Why SR-IOV Shared Port and not vSwitch?
Date: Wed, 28 Jan 2015 01:14:08 +0100 [thread overview]
Message-ID: <54C829D0.5050106@simula.no> (raw)
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
Hello,
I was looking into the InfiniBand SR-IOV implementation and as I see here:
https://www.mail-archive.com/linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg11956.html
the shared port model has been implemented in the drivers.
In an ~5 years old presentation from Liran Liss
(https://www.openfabrics.org/index.php/ofa-documents/doc_view/255-infiniband-and-rocee-virtualization-with-sr-iov.html),
the virtual switch model is briefly mentioned as well.
The disadvantage of the virtual switch model (that is mentioned in the
presentation as well) is the bloated LID space. Is there any other good
reason (or great disadvantage of the the vSwitch model) that the
shared-port has been chosen in favor of the vSwitch?
Vangelis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-01-28 0:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54C829D0.5050106@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.