All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: "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: Thu, 02 Aug 2012 17:15:28 -0600	[thread overview]
Message-ID: <501B0A10.8030703@genband.com> (raw)
In-Reply-To: <20421.1343948491@death.nxdomain>

On 08/02/2012 05:01 PM, Jay Vosburgh wrote:
> Chris Friesen<chris.friesen@genband.com>  wrote:

> 	Still, though, isn't "influence the guest's choice" pretty much
> satisified by having the VF interface go carrier down in the guest when
> the host wants it to?  Or are you thinking about more fine grained than
> that?

That was the first thing we started looking at.

It would actually be better technically (since it would use the 
back-channel between PF and VFs rather than needing an explicit virtual 
network link between host/guest) but it would require work in all the 
PF/VF drivers.  We'd need to get support from all the driver maintainers.

The main advantage of doing it in bonding is that we'd only need to 
modify the code in one place.

Chris

  reply	other threads:[~2012-08-02 23:15 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 [this message]
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

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=501B0A10.8030703@genband.com \
    --to=chris.friesen@genband.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=fubar@us.ibm.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.