From: Chris Friesen <chris.friesen@genband.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: John Fastabend <john.r.fastabend@intel.com>,
Jay Vosburgh <fubar@us.ibm.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [E1000-devel] discussion questions: SR-IOV, virtualization, and bonding
Date: Fri, 10 Aug 2012 12:41:40 -0600 [thread overview]
Message-ID: <502555E4.6060705@genband.com> (raw)
In-Reply-To: <1344016163.2610.9.camel@bwh-desktop.uk.solarflarecom.com>
On 08/03/2012 11:49 AM, Ben Hutchings wrote:
> On Thu, 2012-08-02 at 21:50 -0700, John Fastabend wrote:
>> Perhaps one argument against this is if the hardware supports loopback
>> modes or the edge relay in the hardware is acting like a VEB it may
>> still be possible to support VF to VF traffic even if the external link
>> is down. Not sure how useful this is though or if any existing hardware
>> even supports it.
> [...]
>
> It seems to me that VF to VF traffic ought to still work. If it doesn't
> then that's an unfortunate regression when moving from software bridging
> and virtio to hardware-supported network virtualisation. (But hybrid
> network virtualisation may help to solve that.)
I would have thought this to be desirable as well. Apparently the Intel
engineers disagreed. The 82599 datasheet has the following:
"Loopback is disabled when the network link is disconnected. It is
expected (but not required) that system software (including VMs) does
not post packets for transmission when the link is disconnected. Note
that packets posted by system software for transmission when the link is
down are buffered."
Chris
prev parent reply other threads:[~2012-08-10 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 19:21 discussion questions: SR-IOV, virtualization, and bonding Chris Friesen
2012-08-02 20:30 ` Jay Vosburgh
2012-08-02 22:26 ` Chris Friesen
2012-08-02 22:33 ` Chris Friesen
2012-08-02 23:01 ` [E1000-devel] " Jay Vosburgh
2012-08-02 23:15 ` Chris Friesen
2012-08-02 23:36 ` Jay Vosburgh
2012-08-03 4:50 ` [E1000-devel] " John Fastabend
2012-08-03 17:49 ` Ben Hutchings
2012-08-10 18:41 ` Chris Friesen [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=502555E4.6060705@genband.com \
--to=chris.friesen@genband.com \
--cc=bhutchings@solarflare.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=john.r.fastabend@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.