| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | page_migration.rst | 4 Page migration
7 Page migration allows moving the physical location of pages between
15 The main intent of page migration is to reduce the latency of memory accesses
19 Page migration allows a process to manually relocate the node on which its
25 Page migration functions are provided by the numactl package by Andi Kleen
29 migration. cat ``/proc/<pid>/numa_maps`` allows an easy review of where the
33 Manual migration is useful if for example the scheduler has relocated
37 manual page migration support. Automatic page migration may be implemented
54 Page migration allows the preservation of the relative location of pages
55 within a group of nodes for all migration techniques which will preserve a
[all …]
|
| D | hmm.rst | 25 Finally, the last section presents a new migration helper that allows
106 Shared address space and migration
126 main memory to device memory using existing migration mechanisms and everything
130 memory for the device memory and second to perform migration. Policy decisions
133 Note that any CPU access to a device page triggers a page fault and a migration
136 address A triggers a page fault and initiates a migration back to main memory.
271 Migration to and from device memory
306 The overall migration steps are similar to migrating NUMA pages within system
307 memory (see :ref:`Page migration <page_migration>`) but the steps are split
314 be held for the duration of the migration.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/vm/ |
| D | page_migration.rst | 4 Page migration
7 Page migration allows the moving of the physical location of pages between
12 The main intend of page migration is to reduce the latency of memory access
16 Page migration allows a process to manually relocate the node on which its
22 Page migration functions are provided by the numactl package by Andi Kleen
26 migration. cat ``/proc/<pid>/numa_maps`` allows an easy review of where the
30 Manual migration is useful if for example the scheduler has relocated
34 manual page migration support. Automatic page migration may be implemented
51 Page migration allows the preservation of the relative location of pages
52 within a group of nodes for all migration techniques which will preserve a
[all …]
|
| D | hmm.rst | 25 Finally, the last section presents a new migration helper that allows lever-
106 Shared address space and migration
126 main memory to device memory using existing migration mechanisms and everything
130 memory for the device memory and second to perform migration. Policy decisions
133 Note that any CPU access to a device page triggers a page fault and a migration
136 address A triggers a page fault and initiates a migration back to main memory.
297 which it cannot do. This second callback must trigger a migration back to
301 Migration to and from device memory
304 Because the CPU cannot access device memory, migration must use the device DMA
306 migration helper::
[all …]
|
| /kernel/linux/linux-4.19/mm/ |
| D | migrate.c | 3 * Memory Migration functionality - linux/mm/migrate.c
7 * Page migration was first developed in the context of the memory hotplug
8 * project. The main authors of the migration code are:
109 * compaction threads can race against page migration functions in isolate_movable_page()
113 * being (wrongly) re-isolated while it is under migration, in isolate_movable_page()
161 * from where they were once taken off for compaction/migration.
201 * Restore a potential migration pte to a working pte entry
225 /* PMD-mapped THP migration entry */ in remove_migration_pte()
239 * Recheck VMA as permissions can change since migration started in remove_migration_pte()
287 * Get rid of all migration entries and replace them by
[all …]
|
| D | Kconfig | 189 depends on MIGRATION
217 bool "Allow for balloon memory compaction/migration"
225 by the guest workload. Allowing the compaction & migration for memory
234 select MIGRATION
247 # support for page migration
249 config MIGRATION config
250 bool "Page migration"
254 Allows the migration of the physical location of pages of processes
258 pages as migration can relocate pages to satisfy a huge page
485 select MIGRATION
|
| /kernel/linux/linux-5.10/mm/ |
| D | migrate.c | 3 * Memory Migration functionality - linux/mm/migrate.c
7 * Page migration was first developed in the context of the memory hotplug
8 * project. The main authors of the migration code are:
111 * compaction threads can race against page migration functions in isolate_movable_page()
115 * being (wrongly) re-isolated while it is under migration, in isolate_movable_page()
163 * from where they were once taken off for compaction/migration.
203 * Restore a potential migration pte to a working pte entry
227 /* PMD-mapped THP migration entry */ in remove_migration_pte()
241 * Recheck VMA as permissions can change since migration started in remove_migration_pte()
291 * Get rid of all migration entries and replace them by
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 115 migration. Postcopy live migration is one form of memory
120 migration to QEMU.
128 It is generally beneficial to run one pass of precopy live migration
129 just before starting postcopy live migration, in order to avoid
132 The implementation of postcopy live migration currently uses one
138 in the destination node, into the socket, and the migration thread of
148 by the parallel QEMU migration thread).
156 migration thread in the QEMU running in the destination node will
164 migration around and a single per-page bitmap has to be maintained in
171 postcopy thread just before UFFDIO_COPY|ZEROPAGE runs in the migration
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 167 migration. Postcopy live migration is one form of memory
172 migration to QEMU.
180 It is generally beneficial to run one pass of precopy live migration
181 just before starting postcopy live migration, in order to avoid
184 The implementation of postcopy live migration currently uses one
190 in the destination node, into the socket, and the migration thread of
200 by the parallel QEMU migration thread).
208 migration thread in the QEMU running in the destination node will
216 migration around and a single per-page bitmap has to be maintained in
223 postcopy thread just before ``UFFDIO_COPY|ZEROPAGE`` runs in the migration
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | balloon_compaction.h | 7 * Balloon page migration makes use of the general non-lru movable page
11 * page->mapping is used in context of non-lru page migration to reference
12 * the address space operations for page isolation/migration/compaction.
17 * and safely perform balloon's page compaction and migration we must, always,
33 * compaction / migration.
51 * have to cope for page compaction / migration, as well as it serves the
55 unsigned long isolated_pages; /* # of isolated pages for migration */
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | migrate.h | 15 * - negative errno on page migration failure;
16 * - zero on page migration success;
211 * marked with MIGRATE_PFN_MIGRATE flag in src array unless this is a migration
225 * and properly set the destination entry like for regular migration. Note that
227 * migration was successful for those entry inside the finalize_and_map()
228 * callback just like for regular migration.
234 * The finalize_and_map() callback happens after struct page migration from
236 * memory allocated by the alloc_and_copy() callback). Migration can fail, and
248 * the HMM core will finish up the final steps, and the migration is complete.
|
| D | balloon_compaction.h | 7 * Despite being perfectly possible to perform ballooned pages migration, they
14 * and safely perform balloon's page compaction and migration we must, always,
41 * compaction / migration.
59 * have to cope for page compaction / migration, as well as it serves the
63 unsigned long isolated_pages; /* # of isolated pages for migration */
|
| /kernel/linux/linux-4.19/Documentation/cgroup-v1/ |
| D | memcg_test.txt | 84 The logic is very clear. (About migration, see below)
104 7. Page Migration
137 9.3 Migration
138 For NUMA, migration is an another special case. To do easy test, cpuset
139 is useful. Following is a sample script to do migration.
152 In above set, when you moves a task from 01 to 02, page migration to
176 This is an easy way to test page migration, too.
244 9.9 Move charges at task migration
245 Charges associated with a task can be moved along with task migration.
|
| /kernel/linux/linux-4.19/Documentation/virtual/kvm/devices/ |
| D | vm.txt | 243 Allows userspace to stop migration mode, needed for PGSTE migration.
244 Setting this attribute when migration mode is not active will have no
252 Allows userspace to start migration mode, needed for PGSTE migration.
253 Setting this attribute when migration mode is already active will have
257 Returns: -ENOMEM if there is not enough free memory to start migration mode
263 Allows userspace to query the status of migration mode.
266 the data itself is either 0 if migration mode is disabled or 1
|
| /kernel/linux/linux-4.19/kernel/cgroup/ |
| D | cgroup-internal.h | 57 /* used to track tasks and csets during migration */
72 * Before migration is committed, the target migration tasks are on
75 * or ->dst_csets depending on whether migration is committed.
85 /* migration context also tracks preloading */
89 * atomic success or failure on actual migration.
97 /* subsystems affected by migration */
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 102 The logic is very clear. (About migration, see below)
129 7. Page Migration
171 9.3 Migration
174 For NUMA, migration is an another special case. To do easy test, cpuset
175 is useful. Following is a sample script to do migration::
188 In above set, when you moves a task from 01 to 02, page migration to
220 This is an easy way to test page migration, too.
309 9.9 Move charges at task migration
312 Charges associated with a task can be moved along with task migration.
|
| /kernel/linux/linux-5.10/kernel/cgroup/ |
| D | cgroup-internal.h | 107 /* used to track tasks and csets during migration */
122 * Before migration is committed, the target migration tasks are on
125 * or ->dst_csets depending on whether migration is committed.
135 /* migration context also tracks preloading */
139 * atomic success or failure on actual migration.
147 /* subsystems affected by migration */
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/devices/ |
| D | vm.rst | 288 Allows userspace to stop migration mode, needed for PGSTE migration.
289 Setting this attribute when migration mode is not active will have no
298 Allows userspace to start migration mode, needed for PGSTE migration.
299 Setting this attribute when migration mode is already active will have
303 :Returns: -ENOMEM if there is not enough free memory to start migration mode;
310 Allows userspace to query the status of migration mode.
313 the data itself is either 0 if migration mode is disabled or 1
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | vfio.h | 403 * migration information. Field accesses from this structure are only supported
437 * the migration region should be used to resume the device.
468 * 3. Save the state during live migration
486 * migration region. The sequence to be followed for such transition is given
488 * 3. In live migration of user application, the state transitions from _RUNNING
492 * the device state data to application through the migration region.
495 * through the migration region.
498 * user must not be required to consume all migration data before the device
504 * received through the migration region to resume the device.
515 * The user application should read data_offset field from the migration
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/scripts/python/bin/ |
| D | sched-migration-report | 2 # description: sched migration overview
3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
|
| /kernel/linux/linux-5.10/tools/perf/scripts/python/bin/ |
| D | sched-migration-report | 2 # description: sched migration overview
3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with
76 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
79 net_failover also enables hypervisor controlled live migration to be supported
83 Here is a sample script that shows the steps to initiate live migration on
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with
76 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
79 net_failover also enables hypervisor controlled live migration to be supported
83 Here is a sample script that shows the steps to initiate live migration on
|
| /kernel/linux/linux-4.19/fs/ocfs2/dlm/ |
| D | dlmmaster.c | 839 /* if there is a migration in progress, let the migration in dlm_get_lock_resource()
841 * of the MIGRATION mle: either the migrate finished or in dlm_get_lock_resource()
853 mig ? "MIGRATION" : "BLOCK"); in dlm_get_lock_resource()
1608 mlog(0, "migration mle was found (%u->%u)\n", in dlm_master_request_handler()
1841 " from %u for migration\n", in dlm_assert_master_handler()
1846 " from %u for migration, ignoring\n", in dlm_assert_master_handler()
1948 mlog(0, "finishing off migration of lockres %.*s, " in dlm_assert_master_handler()
1994 * ref given by the master / migration request message. in dlm_assert_master_handler()
2136 * prevent migration from starting while we're still asserting in dlm_assert_master_worker()
2137 * our dominance. The reserved ast delays migration. in dlm_assert_master_worker()
[all …]
|
| /kernel/linux/linux-5.10/fs/ocfs2/dlm/ |
| D | dlmmaster.c | 824 /* if there is a migration in progress, let the migration in dlm_get_lock_resource()
826 * of the MIGRATION mle: either the migrate finished or in dlm_get_lock_resource()
838 mig ? "MIGRATION" : "BLOCK"); in dlm_get_lock_resource()
1593 mlog(0, "migration mle was found (%u->%u)\n", in dlm_master_request_handler()
1826 " from %u for migration\n", in dlm_assert_master_handler()
1831 " from %u for migration, ignoring\n", in dlm_assert_master_handler()
1933 mlog(0, "finishing off migration of lockres %.*s, " in dlm_assert_master_handler()
1979 * ref given by the master / migration request message. in dlm_assert_master_handler()
2121 * prevent migration from starting while we're still asserting in dlm_assert_master_worker()
2122 * our dominance. The reserved ast delays migration. in dlm_assert_master_worker()
[all …]
|