Hi, Tianyu,
I am testing your V2 patch set in our environment, while facing two issues
now. Have a workaround for the first one and hope you could share some light
on the second one :-)
1. Mismatch for ram_block (Have a workaround)
On Fri, Dec 04, 2015 at 02:42:36PM +0800, Lan, Tianyu wrote:
>
> On 12/2/2015 10:31 PM, Michael S. Tsirkin wrote:
> >>>We hope
> >>>to find a better way to make SRIOV NIC work in these cases and this is
> >>>worth to do since SRIOV NIC provides better network performance compared
> >>>with PV
On 12/4/2015 4:05 PM, Michael S. Tsirkin wrote:
I haven't read it, but I would like to note you can't rely on research
papers. If you propose a patch to be merged you need to measure what is
its actual effect on modern linux at the end of 2015.
Sure. Will do that.
On 12/2/2015 10:31 PM, Michael S. Tsirkin wrote:
>We hope
>to find a better way to make SRIOV NIC work in these cases and this is
>worth to do since SRIOV NIC provides better network performance compared
>with PV NIC.
If this is a performance optimization as the above implies,
you need to
On 12/2/2015 10:31 PM, Michael S. Tsirkin wrote:
>We hope
>to find a better way to make SRIOV NIC work in these cases and this is
>worth to do since SRIOV NIC provides better network performance compared
>with PV NIC.
If this is a performance optimization as the above implies,
you need to
On Wed, Dec 2, 2015 at 6:08 AM, Lan, Tianyu wrote:
> On 12/1/2015 11:02 PM, Michael S. Tsirkin wrote:
>>>
>>> But
>>> it requires guest OS to do specific configurations inside and rely on
>>> bonding driver which blocks it work on Windows.
>>> From performance side,
>>>
On Wed, Dec 02, 2015 at 10:08:25PM +0800, Lan, Tianyu wrote:
> On 12/1/2015 11:02 PM, Michael S. Tsirkin wrote:
> >>But
> >>it requires guest OS to do specific configurations inside and rely on
> >>bonding driver which blocks it work on Windows.
> >> From performance side,
> >>putting VF and
On 12/1/2015 11:02 PM, Michael S. Tsirkin wrote:
But
it requires guest OS to do specific configurations inside and rely on
bonding driver which blocks it work on Windows.
From performance side,
putting VF and virtio NIC under bonded interface will affect their
performance even when not do
On Tue, Dec 01, 2015 at 02:26:57PM +0800, Lan, Tianyu wrote:
>
>
> On 11/30/2015 4:01 PM, Michael S. Tsirkin wrote:
> >It is still not very clear what it is you are trying to achieve, and
> >whether your patchset achieves it. You merely say "adding live
> >migration" but it seems pretty clear
On 11/30/2015 4:01 PM, Michael S. Tsirkin wrote:
It is still not very clear what it is you are trying to achieve, and
whether your patchset achieves it. You merely say "adding live
migration" but it seems pretty clear this isn't about being able to
migrate a guest transparently, since you are
On Tue, Nov 24, 2015 at 09:35:17PM +0800, Lan Tianyu wrote:
> This patchset is to propose a solution of adding live migration
> support for SRIOV NIC.
>
> During migration, Qemu needs to let VF driver in the VM to know
> migration start and end. Qemu adds faked PCI migration capability
> to help
This patchset is to propose a solution of adding live migration
support for SRIOV NIC.
During migration, Qemu needs to let VF driver in the VM to know
migration start and end. Qemu adds faked PCI migration capability
to help to sync status between two sides during migration.
Qemu triggers VF's
12 matches
Mail list logo