From: Matthew Monaco <Matthew.Monaco@Colorado•EDU>
To: Or Gerlitz <gerlitz.or@gmail•com>
Cc: Linux Netdev List <netdev@vger•kernel.org>
Subject: Re: sr-iov and bridges (mlx4)
Date: Sun, 20 Sep 2015 10:21:18 -0600 [thread overview]
Message-ID: <55FEDCFE.30506@colorado.edu> (raw)
In-Reply-To: <CAJ3xEMg1HR+WfhUNMCu9mnXp6F9Vuw8=VkrUvcynAn3VWoP2Gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On 09/20/2015 05:01 AM, Or Gerlitz wrote:
> On Sun, Sep 20, 2015 at 2:58 AM, Matthew Monaco
> <Matthew.Monaco@colorado•edu> wrote:
> [...]
>> In all cases, VMs with SR-IOV work fine, IP on the host works fine, outbound
>> DHCP from the virtio VMs work fine, but inbound frames are not making it back to
>> the VM.
> [...]
>> Is there a know limitation of mixing SR-IOV and bridges in general? Does the
>> SR-IOV switch specific to the mlx4 hardware not work well with linux bridges? ...?
>
> It would be a bit hard for bridge based promiscuous environment to work OOB
> for one of the functions (PF or VF) in SRIOV, this is generic issue,
> and not related
> to specific vendor.
>
> You need to use the bridge (8) tool (part of iproute2) and add the P.V
> VM MACs to
> the PF interface as "self" see some slides (21/22/23) from netdev 0.1
> that deal with that
> https://netdev01.org/docs/netdev_tutorial_bridge_makita_150213.pdf
>
> Or.
>
> It also possible to mark one bridge port (the PF) as non-promiscuous,
> but I haven't
> played with that myself yet (slide 32), so can't just send you doing it...
>
Many thanks, that helps. Now to figure out the best approach for shoving this
into OpenStack =)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-20 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 23:58 sr-iov and bridges (mlx4) Matthew Monaco
2015-09-20 11:01 ` Or Gerlitz
2015-09-20 16:21 ` Matthew Monaco [this message]
2015-09-20 18:18 ` Nieścierowicz Adam
2015-09-20 18:45 ` Matthew Monaco
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=55FEDCFE.30506@colorado.edu \
--to=matthew.monaco@colorado$(echo .)edu \
--cc=gerlitz.or@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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