[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEHy93JG-X-5qtrU2wUmxfMzKc9G3GDNL_H-FXsmAmfwvoO+vg@mail.gmail.com>
Date: Thu, 7 Dec 2017 09:28:58 +0200
From: achiad shochat <achiad.mellanox@...il.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Alexander Duyck <alexander.duyck@...il.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
Hannes Frederic Sowa <hannes@...hat.com>,
Sridhar Samudrala <sridhar.samudrala@...el.com>,
netdev <netdev@...r.kernel.org>,
virtualization@...ts.linux-foundation.org,
Achiad <achiad@...lanox.com>,
Peter Waskiewicz Jr <peter.waskiewicz.jr@...el.com>,
"Singhai, Anjali" <anjali.singhai@...el.com>,
Shannon Nelson <shannon.nelson@...cle.com>,
Andy Gospodarek <gospo@...adcom.com>,
Or Gerlitz <gerlitz.or@...il.com>
Subject: Re: [RFC] virtio-net: help live migrate SR-IOV devices
On 5 December 2017 at 21:20, Michael S. Tsirkin <mst@...hat.com> wrote:
> On Tue, Dec 05, 2017 at 11:59:17AM +0200, achiad shochat wrote:
>> Then we'll have a single solution for both netvsc and virtio (and any
>> other PV device).
>> And we could handle the VF DMA dirt issue agnostically.
>
> For the record, I won't block patches adding this kist to virtio
> on the basis that they must be generic. It's not a lot
> of code, implementation can come first, prettify later.
It's not a lot of code either way.
So I fail to understand why not to do it right from the beginning.
For the record...
>
> But we do need to have a discussion about how devices are paired.
> I am not sure using just MAC works. E.g. some passthrough
> devices don't give host ability to set the MAC.
> Are these worth worrying about?
>
> --
> MST
Powered by blists - more mailing lists