[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 16/16] migration/multifd: Move nocomp code into multifd-no
|
From: |
Peter Xu |
|
Subject: |
Re: [PATCH v4 16/16] migration/multifd: Move nocomp code into multifd-nocomp.c |
|
Date: |
Mon, 26 Aug 2024 12:16:17 -0400 |
On Fri, Aug 23, 2024 at 02:39:11PM -0300, Fabiano Rosas wrote:
> In preparation for adding new payload types to multifd, move most of
> the no-compression code into multifd-nocomp.c. Let's try to keep a
> semblance of layering by not mixing general multifd control flow with
> the details of transmitting pages of ram.
>
> There are still some pieces leftover, namely the p->normal, p->zero,
> etc variables that we use for zero page tracking and the packet
> allocation which is heavily dependent on the ram code.
>
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
- [PATCH v4 11/16] migration/multifd: Don't send ram data during SYNC, (continued)
- [PATCH v4 11/16] migration/multifd: Don't send ram data during SYNC, Fabiano Rosas, 2024/08/23
- [PATCH v4 12/16] migration/multifd: Replace multifd_send_state->pages with client data, Fabiano Rosas, 2024/08/23
- [PATCH v4 13/16] migration/multifd: Allow multifd sync without flush, Fabiano Rosas, 2024/08/23
- [PATCH v4 15/16] migration/multifd: Register nocomp ops dynamically, Fabiano Rosas, 2024/08/23
- [PATCH v4 14/16] migration/multifd: Standardize on multifd ops names, Fabiano Rosas, 2024/08/23
- [PATCH v4 16/16] migration/multifd: Move nocomp code into multifd-nocomp.c, Fabiano Rosas, 2024/08/23
- Re: [PATCH v4 16/16] migration/multifd: Move nocomp code into multifd-nocomp.c,
Peter Xu <=