[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 15/16] migration/multifd: Register nocomp ops dynamically
|
From: |
Peter Xu |
|
Subject: |
Re: [PATCH v4 15/16] migration/multifd: Register nocomp ops dynamically |
|
Date: |
Mon, 26 Aug 2024 12:15:30 -0400 |
On Fri, Aug 23, 2024 at 02:39:10PM -0300, Fabiano Rosas wrote:
> Prior to moving the ram code into multifd-nocomp.c, change the code to
> register the nocomp ops dynamically so we don't need to have the ops
> structure defined in multifd.c.
>
> While here, move the ops struct initialization to the end of the file
> to make the next diff cleaner.
>
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
- [PATCH v4 10/16] migration/multifd: Isolate ram pages packet data, (continued)
- [PATCH v4 10/16] migration/multifd: Isolate ram pages packet data, Fabiano Rosas, 2024/08/23
- [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