Searched hist:d117ed06 (Results 1 – 3 of 3) sorted by relevance
/qemu/migration/ |
H A D | file.c | d117ed06 Thu Feb 29 15:30:09 GMT 2024 Fabiano Rosas <farosas@suse.de> migration/multifd: Allow receiving pages without packets
Currently multifd does not need to have knowledge of pages on the receiving side because all the information needed is within the packets that come in the stream.
We're about to add support to mapped-ram migration, which cannot use packets because it expects the ramblock section in the migration file to contain only the guest pages data.
Add a data structure to transfer pages between the ram migration code and the multifd receiving threads.
We don't want to reuse MultiFDPages_t for two reasons:
a) multifd threads don't really need to know about the data they're receiving.
b) the receiving side has to be stopped to load the pages, which means we can experiment with larger granularities than page size when transferring data.
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240229153017.2221-16-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com> d117ed06 Thu Feb 29 15:30:09 GMT 2024 Fabiano Rosas <farosas@suse.de> migration/multifd: Allow receiving pages without packets
Currently multifd does not need to have knowledge of pages on the receiving side because all the information needed is within the packets that come in the stream.
We're about to add support to mapped-ram migration, which cannot use packets because it expects the ramblock section in the migration file to contain only the guest pages data.
Add a data structure to transfer pages between the ram migration code and the multifd receiving threads.
We don't want to reuse MultiFDPages_t for two reasons:
a) multifd threads don't really need to know about the data they're receiving.
b) the receiving side has to be stopped to load the pages, which means we can experiment with larger granularities than page size when transferring data.
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240229153017.2221-16-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com>
|
H A D | multifd.h | d117ed06 Thu Feb 29 15:30:09 GMT 2024 Fabiano Rosas <farosas@suse.de> migration/multifd: Allow receiving pages without packets
Currently multifd does not need to have knowledge of pages on the receiving side because all the information needed is within the packets that come in the stream.
We're about to add support to mapped-ram migration, which cannot use packets because it expects the ramblock section in the migration file to contain only the guest pages data.
Add a data structure to transfer pages between the ram migration code and the multifd receiving threads.
We don't want to reuse MultiFDPages_t for two reasons:
a) multifd threads don't really need to know about the data they're receiving.
b) the receiving side has to be stopped to load the pages, which means we can experiment with larger granularities than page size when transferring data.
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240229153017.2221-16-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com> d117ed06 Thu Feb 29 15:30:09 GMT 2024 Fabiano Rosas <farosas@suse.de> migration/multifd: Allow receiving pages without packets
Currently multifd does not need to have knowledge of pages on the receiving side because all the information needed is within the packets that come in the stream.
We're about to add support to mapped-ram migration, which cannot use packets because it expects the ramblock section in the migration file to contain only the guest pages data.
Add a data structure to transfer pages between the ram migration code and the multifd receiving threads.
We don't want to reuse MultiFDPages_t for two reasons:
a) multifd threads don't really need to know about the data they're receiving.
b) the receiving side has to be stopped to load the pages, which means we can experiment with larger granularities than page size when transferring data.
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240229153017.2221-16-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com>
|
H A D | multifd.c | d117ed06 Thu Feb 29 15:30:09 GMT 2024 Fabiano Rosas <farosas@suse.de> migration/multifd: Allow receiving pages without packets
Currently multifd does not need to have knowledge of pages on the receiving side because all the information needed is within the packets that come in the stream.
We're about to add support to mapped-ram migration, which cannot use packets because it expects the ramblock section in the migration file to contain only the guest pages data.
Add a data structure to transfer pages between the ram migration code and the multifd receiving threads.
We don't want to reuse MultiFDPages_t for two reasons:
a) multifd threads don't really need to know about the data they're receiving.
b) the receiving side has to be stopped to load the pages, which means we can experiment with larger granularities than page size when transferring data.
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240229153017.2221-16-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com> d117ed06 Thu Feb 29 15:30:09 GMT 2024 Fabiano Rosas <farosas@suse.de> migration/multifd: Allow receiving pages without packets
Currently multifd does not need to have knowledge of pages on the receiving side because all the information needed is within the packets that come in the stream.
We're about to add support to mapped-ram migration, which cannot use packets because it expects the ramblock section in the migration file to contain only the guest pages data.
Add a data structure to transfer pages between the ram migration code and the multifd receiving threads.
We don't want to reuse MultiFDPages_t for two reasons:
a) multifd threads don't really need to know about the data they're receiving.
b) the receiving side has to be stopped to load the pages, which means we can experiment with larger granularities than page size when transferring data.
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240229153017.2221-16-farosas@suse.de Signed-off-by: Peter Xu <peterx@redhat.com>
|