From: Ben Hutchings <ben@decadent.org.uk>
To: yoann.juet@univ-nantes.fr
Cc: netdev@vger.kernel.org, Ariel Elior <ariele@broadcom.com>
Subject: Re: bnx2x + SR-IOV, no internal L2 switching
Date: Wed, 12 Feb 2014 23:10:40 +0000 [thread overview]
Message-ID: <1392246640.15615.37.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <52FB7843.6050601@univ-nantes.fr>
[-- Attachment #1: Type: text/plain, Size: 1798 bytes --]
On Wed, 2014-02-12 at 14:33 +0100, Yoann Juet wrote:
> Hi all,
>
> I'm conducting experiments on SR-IOV with Broadcom and Intel cards on
> debian/unstable with KVM hypervisor. On Broadcom cards (bnx2x module,
> BCM57810 devices), Virtual Functions (VFs) get running, Virtual Machines
> attached to such VFs inherit network connectivity with excellent
> performance.
>
> However, VMs attached to VFs on the Broadcom Physical Functions (PFs)
> behave like they were connected to an ancient hub, not a L2 switch. It
> is as if there was no internal L2 switching on the Broadcom card to
> process VF <-> VF or VF <-> PF communications. As a result, a VM sees
> all inbound/outbound traffic from/to others VMs as well as traffic
> destined to the PF (for instance, the physical ethX has an IP address).
Are you're using the ISC DHCP client, which puts the interface in
promiscuous mode? If the Broadcom NIC supports promiscuous mode on VFs,
that may explain what you're seeing.
> On the other hand, everything works like a charm with Intel cards (ixgbe
> module, 82599EB devices). Traffic between VFs or VF/PF is switched
> internally by the card.
I think these VFs don't support promiscuous mode. Anyway, the ixgbevf
driver silently ignores it.
Ben.
> I found very little literature about SR-IOV on Broadcom devices. I
> wonder if it's a normal behaviour, a misconfiguration on my side or
> perhaps a firmware/driver bug.
>
> Have you seen this issue before ?
>
> ---
> Kernel 3.12.9 (same behaviour with kernels 3.10.x)
> driver: bnx2x
> firmware-version: 7.8.17
> Debian/unstable
> libvirt 1.2.1
> QEMU 1.7.0
> ---
>
> Best regards,
--
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-02-12 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 13:33 bnx2x + SR-IOV, no internal L2 switching Yoann Juet
2014-02-12 14:38 ` Ariel Elior
2014-02-12 15:54 ` Yoann Juet
2014-02-12 23:10 ` Ben Hutchings [this message]
2014-02-13 9:42 ` Yoann Juet
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=1392246640.15615.37.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=ariele@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=yoann.juet@univ-nantes.fr \
/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