netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
	Hannes Frederic Sowa <hannes@redhat.com>,
	achiad shochat <achiad.mellanox@gmail.com>,
	Sridhar Samudrala <sridhar.samudrala@intel.com>,
	virtualization@lists.linux-foundation.org,
	Shannon Nelson <shannon.nelson@oracle.com>,
	Achiad <achiad@mellanox.com>,
	Peter Waskiewicz Jr <peter.waskiewicz.jr@intel.com>,
	netdev <netdev@vger.kernel.org>,
	"Singhai, Anjali" <anjali.singhai@intel.com>,
	Andy Gospodarek <gospo@broadcom.com>,
	Or Gerlitz <gerlitz.or@gmail.com>
Subject: Re: [RFC] virtio-net: help live migrate SR-IOV devices
Date: Thu, 7 Dec 2017 18:53:05 +0200	[thread overview]
Message-ID: <20171207184829-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAKgT0UfC2o4P8DeRHnnPV9fvUzJYbkCKVHr=zHOfbEQdLn=3nA@mail.gmail.com>

On Thu, Dec 07, 2017 at 08:45:33AM -0800, Alexander Duyck wrote:
> As far as indicating that the interfaces are meant to be enslaved I
> wonder if we couldn't look at tweaking the PCI layout of the guest and
> use that to indicate that a given set of interfaces are meant to be
> bonded. For example the VFs are all meant to work as a part of a
> multi-function device. What if we were to make virtio-net function 0
> of a PCI/PCIe device, and then place any direct assigned VFs that are
> meant to be a part of the bond in functions 1-7 of the device? Then it
> isn't too far off from the model we have on the host where if the VF
> goes away we would expect to see the traffic on the PF that is usually
> occupying function 0 of a given device.

This pretty much precludes removing them with hotplug.

But as long as we are happy to limit this to pci devices,
maybe we should put them behind a pci bridge.

All devices behind a bridge would be assumed to have
the same backend.

QEMU has pci-bridge-seat which we could reuse for this -
just need to build a similar pci express bridge.

-- 
MST

  reply	other threads:[~2017-12-07 16:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171128112722.00003716@intel.com>
2017-11-30  3:29 ` [RFC] virtio-net: help live migrate SR-IOV devices Jason Wang
2017-11-30  3:51   ` Jakub Kicinski
2017-11-30  4:10     ` Stephen Hemminger
2017-11-30  4:21       ` Jakub Kicinski
2017-11-30 13:54     ` Michael S. Tsirkin
2017-11-30 20:48       ` Jakub Kicinski
2017-12-01  5:13         ` Michael S. Tsirkin
2017-11-30  8:08   ` achiad shochat
2017-11-30 14:11     ` Michael S. Tsirkin
2017-12-01 20:08       ` Shannon Nelson
2017-12-03  5:05         ` Michael S. Tsirkin
2017-12-03  9:14           ` achiad shochat
2017-12-03 17:35             ` Stephen Hemminger
2017-12-04  9:51               ` achiad shochat
2017-12-04 16:30                 ` Alexander Duyck
2017-12-05  9:59                   ` achiad shochat
2017-12-05 19:20                     ` Michael S. Tsirkin
2017-12-05 21:52                       ` Jesse Brandeburg
2017-12-05 22:05                         ` Michael S. Tsirkin
2017-12-07  7:28                       ` achiad shochat
2017-12-07 16:45                         ` Alexander Duyck
2017-12-07 16:53                           ` Michael S. Tsirkin [this message]
2017-12-05 22:29                     ` Jakub Kicinski
2017-12-05 22:41                       ` Stephen Hemminger
2017-11-30 14:14   ` Michael S. Tsirkin

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=20171207184829-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=achiad.mellanox@gmail.com \
    --cc=achiad@mellanox.com \
    --cc=alexander.duyck@gmail.com \
    --cc=anjali.singhai@intel.com \
    --cc=gerlitz.or@gmail.com \
    --cc=gospo@broadcom.com \
    --cc=hannes@redhat.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=peter.waskiewicz.jr@intel.com \
    --cc=shannon.nelson@oracle.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=virtualization@lists.linux-foundation.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).