From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
netdev@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
David Miller <davem@davemloft.net>
Subject: Re: 2.6.31 ARP related problems
Date: Thu, 03 Sep 2009 11:04:21 +0300 [thread overview]
Message-ID: <4A9F7885.8080402@Voltaire.com> (raw)
In-Reply-To: <5f2db9d90909020747k23be99d3xc27d6c668351bf60@mail.gmail.com>
Alexander Duyck wrote:
> I don't suspect this has much of an effect on the Virtualization use case for SR-IOV since the VFs are meant to be direct assigned as PCI devices to the individual VMs
I understand that eventually there will be scheme when VFs will be
directly assigned to the VM, but there are/will be many occasions where
a VF will serve as a virtual NIC in a Linux system e.g one serving as a
host but also other purposes (think on macvlan as "software SR-IOV"
where with your HW its the real thing).
> You can probably also reproduce the issue by placing multiple physical network interfaces on the same network segment if you saw the same effect on SR-IOV since that is essentially the effect the VFs create due to the switching logic built into the 82576
Yes, as I managed to produce it with thee schemes: macvlan, veth+bridge
and SR-IOV, I believe something is just broken wrt to ARP replies in
2.6.31 which is now in its rc8! I will try to look on that, and
hopefully we can fix it at least for -stable.
Or.
I wasn't sure to understand your "the effect the VFs create due to the
switching logic built into the 82576" comment, can you elaborate more on
that?
next prev parent reply other threads:[~2009-09-03 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 11:30 2.6.31 ARP related problems with multiple macvlan NICs Or Gerlitz
2009-09-01 13:20 ` Eric W. Biederman
2009-09-02 12:20 ` 2.6.31 ARP related problems Or Gerlitz
2009-09-02 14:47 ` Alexander Duyck
2009-09-03 8:04 ` Or Gerlitz [this message]
2009-09-03 16:07 ` Duyck, Alexander H
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=4A9F7885.8080402@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).