From: Or Gerlitz <ogerlitz@Voltaire.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: 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: Wed, 02 Sep 2009 15:20:11 +0300 [thread overview]
Message-ID: <4A9E62FB.6090000@Voltaire.com> (raw)
In-Reply-To: <m163c2ztrf.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> I just tested. If the two macvlans are in separate network namespaces all is well,
> so definitely not macvlan. As you have observed there are no real changes to arp.c
Yes, it's not macvlan to blame, I just tested it in SR-IOV scheme with igb/igbvf and
I see the same problem, only ping that goes through / targeted to the IP address of the first
VF device routing hit works, which means SR-IOV isn't really usable with 2.6.31 when you want
a multiple VMs scheme, each attached to a different VF and all VMs on the same network segment.
Or.
next prev parent reply other threads:[~2009-09-02 12:20 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 ` Or Gerlitz [this message]
2009-09-02 14:47 ` 2.6.31 ARP related problems Alexander Duyck
2009-09-03 8:04 ` Or Gerlitz
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=4A9E62FB.6090000@Voltaire.com \
--to=ogerlitz@voltaire.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).