From: Matthew Monaco <Matthew.Monaco@Colorado•EDU>
To: Linux Netdev List <netdev@vger•kernel.org>
Cc: adam.niescierowicz@justnet•pl
Subject: Re: sr-iov and bridges (mlx4)
Date: Sun, 20 Sep 2015 12:45:14 -0600 [thread overview]
Message-ID: <55FEFEBA.6020903@colorado.edu> (raw)
In-Reply-To: <8f15ec904f631f2d792388128b34732a@justnet.pl>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On 09/20/2015 12:18 PM, Nieścierowicz Adam wrote:
> Hi Matthew,
> in near future i want to do exactly the same, if you make progress with
> SR-IOV+Bridge+OpenStack please leave here some advice.
>
I wrote a shell script which polls (~15s) each bridge /sys/class/net/brq*, and
for each bridge figures out the uplink (not named
/sys/class/net/brq*/brif/tap*). Then, for each port
/sys/class/net/<bridge>/brif/tap*, determine the VM mac address and add an fdb
entry if it doesn't already exist. In my environment, it seems the VM mac is the
tap mac s/^fe:/fa:/.
This is a little messier than the non-promsicuous bridge option, but I wasn't
able to get that working on CentOS7/kernel-ml-4.2/iproute-3.10. But either way,
this won't work well if you're trying to do nested virt, which thankfully I
don't need at this time.
If you're interested I can attach the script and systemd unit. Otherwise, I'll
be looking to try to get this handled properly by neutron-linuxbridge-agent.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-09-20 18:45 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
2015-09-20 18:18 ` Nieścierowicz Adam
2015-09-20 18:45 ` Matthew Monaco [this message]
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=55FEFEBA.6020903@colorado.edu \
--to=matthew.monaco@colorado$(echo .)edu \
--cc=adam.niescierowicz@justnet$(echo .)pl \
--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