/Linux-v6.6/Documentation/mm/ |
D | page_migration.rst | 2 Page migration 5 Page migration allows moving the physical location of pages between 13 The main intent of page migration is to reduce the latency of memory accesses 17 Page migration allows a process to manually relocate the node on which its 23 Page migration functions are provided by the numactl package by Andi Kleen 27 migration. cat ``/proc/<pid>/numa_maps`` allows an easy review of where the 31 Manual migration is useful if for example the scheduler has relocated 35 manual page migration support. Automatic page migration may be implemented 52 Page migration allows the preservation of the relative location of pages 53 within a group of nodes for all migration techniques which will preserve a [all …]
|
D | hmm.rst | 23 Finally, the last section presents a new migration helper that allows 104 Shared address space and migration 124 main memory to device memory using existing migration mechanisms and everything 128 memory for the device memory and second to perform migration. Policy decisions 131 Note that any CPU access to a device page triggers a page fault and a migration 134 address A triggers a page fault and initiates a migration back to main memory. 295 The overall migration steps are similar to migrating NUMA pages within system 303 be held for the duration of the migration. 336 the LRU), unmapped from the process, and a special migration PTE is 367 This step is where the migration is actually "committed". [all …]
|
D | arch_pgtable_helpers.rst | 257 | is_migration_entry | Tests a migration (read or write) swapped entry | 259 | is_writable_migration_entry | Tests a write migration swapped entry | 261 | make_readable_migration_entry | Creates a read migration swapped entry | 263 | make_writable_migration_entry | Creates a write migration swapped entry |
|
/Linux-v6.6/tools/testing/selftests/mm/ |
D | migration.c | 23 FIXTURE(migration) in FIXTURE() argument 32 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument 57 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument 118 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME) 143 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME) 178 TEST_F_TIMEOUT(migration, private_anon_thp, 2*RUNTIME)
|
D | run_vmtests.sh | 63 - migration 64 invoke move_pages(2) to exercise the migration entry code 354 CATEGORY="migration" run_test ./migration
|
D | .gitignore | 14 migration
|
D | Makefile | 55 TEST_GEN_FILES += migration 182 $(OUTPUT)/migration: LDLIBS += -lnuma
|
/Linux-v6.6/Documentation/ABI/testing/ |
D | sysfs-kernel-mm-numa | 11 Page migration during reclaim is intended for systems 16 Allowing page migration during reclaim enables these 18 when the fast tier is under pressure. This migration
|
D | sysfs-class-rnbd-client | 14 > [access_mode=<ro|rw|migration>] > map_device 27 [access_mode=<ro|rw|migration>] 82 a device to be exported in rw mode only once. The "migration"
|
/Linux-v6.6/Documentation/networking/ |
D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with 65 be brought UP during live migration to allow uninterrupted communication. 116 net_failover also enables hypervisor controlled live migration to be supported 120 Here is a sample script that shows the steps to initiate live migration from 165 # Clean up FDB entries after migration completes. 169 On the destination hypervisor, a shared bridge 'br0' is created before migration 173 The following script is executed on the destination hypervisor once migration
|
D | failover.rst | 17 datapath. It also allows live migration of VMs with direct attached VFs by
|
/Linux-v6.6/Documentation/admin-guide/cgroup-v1/ |
D | memcg_test.rst | 102 The logic is very clear. (About migration, see below) 165 For NUMA, migration is an another special case. To do easy test, cpuset 166 is useful. Following is a sample script to do migration:: 179 In above set, when you moves a task from 01 to 02, page migration to 211 This is an easy way to test page migration, too. 298 9.9 Move charges at task migration 301 Charges associated with a task can be moved along with task migration.
|
D | rdma.rst | 53 always owned by the creator cgroup css. This allows process migration from one 57 deleted after processes migrated. This allow progress migration as well with
|
/Linux-v6.6/Documentation/virt/kvm/devices/ |
D | vm.rst | 291 Allows userspace to stop migration mode, needed for PGSTE migration. 292 Setting this attribute when migration mode is not active will have no 301 Allows userspace to start migration mode, needed for PGSTE migration. 302 Setting this attribute when migration mode is already active will have 306 dirty tracking is disabled on any memslot, migration mode is automatically 310 :Returns: -ENOMEM if there is not enough free memory to start migration mode; 317 Allows userspace to query the status of migration mode. 320 the data itself is either 0 if migration mode is disabled or 1
|
/Linux-v6.6/fs/proc/ |
D | task_mmu.c | 442 bool migration) in smaps_account() argument 480 if ((page_count(page) == 1) || migration) { in smaps_account() 529 bool migration = false, young = false, dirty = false; in smaps_pte_entry() local 554 migration = true; in smaps_pte_entry() 565 smaps_account(mss, page, false, young, dirty, locked, migration); in smaps_pte_entry() 576 bool migration = false; in smaps_pmd_entry() local 584 migration = true; in smaps_pmd_entry() 600 locked, migration); in smaps_pmd_entry() 1410 bool migration = false; in pte_to_pagemap_entry() local 1442 migration = is_migration_entry(entry); in pte_to_pagemap_entry() [all …]
|
/Linux-v6.6/tools/perf/scripts/python/bin/ |
D | sched-migration-report | 3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
|
/Linux-v6.6/Documentation/driver-api/ |
D | vfio-pci-device-specific-driver-acceptance.rst | 16 state for the purposes of supporting migration. 30 extensions, for example in the case of migration data, how is the
|
/Linux-v6.6/Documentation/admin-guide/mm/ |
D | userfaultfd.rst | 257 the VM to another physical machine. Since we want the migration to be 266 migration. Postcopy live migration is one form of memory 271 migration to QEMU. 279 It is generally beneficial to run one pass of precopy live migration 280 just before starting postcopy live migration, in order to avoid 283 The implementation of postcopy live migration currently uses one 289 in the destination node, into the socket, and the migration thread of 299 by the parallel QEMU migration thread). 307 migration thread in the QEMU running in the destination node will 315 migration around and a single per-page bitmap has to be maintained in [all …]
|
/Linux-v6.6/drivers/vfio/pci/mlx5/ |
D | Kconfig | 7 This provides migration support for MLX5 devices using the VFIO
|
/Linux-v6.6/kernel/irq/ |
D | Makefile | 13 obj-$(CONFIG_GENERIC_PENDING_IRQ) += migration.o
|
/Linux-v6.6/drivers/gpu/drm/amd/amdkfd/ |
D | kfd_smi_events.h | 36 unsigned long address, bool migration);
|
/Linux-v6.6/Documentation/powerpc/ |
D | dawr-power9.rst | 43 migration from POWER8 to POWER9, at the cost of silently losing the 44 DAWR on the migration.
|
/Linux-v6.6/include/scsi/ |
D | viosrp.h | 188 struct mad_migration_cap migration; member
|
/Linux-v6.6/fs/nfs/ |
D | Kconfig | 144 bool "NFSv4.1 client support for migration" 149 it can support NFSv4 migration. 151 The NFSv4.1 pieces of the Linux NFSv4 migration implementation are
|
/Linux-v6.6/Documentation/virt/hyperv/ |
D | clocks.rst | 44 at a constant 10 MHz frequency. In the case of a live migration 50 support for TSC frequency scaling to enable live migration of VMs
|