From: Yishai Hadas <yishaih@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: <mst@redhat.com>, <jasowang@redhat.com>, <kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>, <parav@nvidia.com>,
<feliu@nvidia.com>, <kevin.tian@intel.com>,
<joao.m.martins@oracle.com>, <leonro@nvidia.com>,
<maorg@nvidia.com>
Subject: Re: [PATCH vfio 0/7] Enhances the vfio-virtio driver to support live migration
Date: Tue, 29 Oct 2024 13:59:15 +0200 [thread overview]
Message-ID: <852d7d45-8ffc-4d94-89d3-209dbc8bfa34@nvidia.com> (raw)
In-Reply-To: <20241028162354.GS6956@nvidia.com>
On 28/10/2024 18:23, Jason Gunthorpe wrote:
> On Mon, Oct 28, 2024 at 10:13:48AM -0600, Alex Williamson wrote:
>> On Sun, 27 Oct 2024 12:07:44 +0200
>> Yishai Hadas <yishaih@nvidia.com> wrote:
>> If the virtio spec doesn't support partial contexts, what makes it
>> beneficial here?
>
> It stil lets the receiver 'warm up', like allocating memory and
> approximately sizing things.
>
>> If it is beneficial, why is it beneficial to send initial data more than
>> once?
>
> I guess because it is allowed to change and the benefit is highest
> when the pre copy data closely matches the final data..
>
> Rate limiting does seem better to me
>
> Jason
Right, given that the device state is likely to remain mostly unchanged
over a certain period, using a rate limiter could be a sensible approach.
So, in V1, I plan to replace the hard-coded limit value of 128 with a
rate limiter by reporting no data available for some time interval after
the previous call.
I would start with a one second interval, which seems to be reasonable
for that kind of device.
Yishai
next prev parent reply other threads:[~2024-10-29 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 10:07 [PATCH vfio 0/7] Enhances the vfio-virtio driver to support live migration Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 1/7] virtio_pci: Introduce device parts access commands Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 2/7] virtio: Extend the admin command to include the result size Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 3/7] virtio: Manage device and driver capabilities via the admin commands Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 4/7] virtio-pci: Introduce APIs to execute device parts " Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 5/7] vfio/virtio: Add support for the basic live migration functionality Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 6/7] vfio/virtio: Add PRE_COPY support for live migration Yishai Hadas
2024-10-27 10:07 ` [PATCH vfio 7/7] vfio/virtio: Enable live migration once VIRTIO_PCI was configured Yishai Hadas
2024-10-28 16:13 ` [PATCH vfio 0/7] Enhances the vfio-virtio driver to support live migration Alex Williamson
2024-10-28 16:23 ` Jason Gunthorpe
2024-10-28 16:54 ` Alex Williamson
2024-10-28 17:46 ` Parav Pandit
2024-10-29 20:28 ` Alex Williamson
2024-10-31 15:04 ` Parav Pandit
2024-11-01 16:25 ` Alex Williamson
2024-11-03 14:38 ` Parav Pandit
2024-10-29 11:59 ` Yishai Hadas [this message]
2024-10-28 18:17 ` Alex Williamson
2024-10-29 8:43 ` Yishai Hadas
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=852d7d45-8ffc-4d94-89d3-209dbc8bfa34@nvidia.com \
--to=yishaih@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=feliu@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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