| /linux-5.19.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.
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.
347 the LRU), unmapped from the process, and a special migration PTE is
[all …]
|
| D | arch_pgtable_helpers.rst | 251 | is_migration_entry | Tests a migration (read or write) swapped entry |
253 | is_writable_migration_entry | Tests a write migration swapped entry |
255 | make_readable_migration_entry | Creates a read migration swapped entry |
257 | make_writable_migration_entry | Creates a write migration swapped entry |
|
| D | unevictable-lru.rst | 84 detected by isolate_lru_page(), we would prevent their migration.
231 available to the migration subsystem.
243 put to work, without preventing the migration of mlocked pages. This is why
396 replaced with an entry that refers to the new page. Linux supports migration
399 new page is mapped in place of migration entry in a VM_LOCKED VMA. If the page
403 Note that page migration can race with mlocking or munlocking of the same page.
404 There is mostly no problem since page migration requires unmapping all PTEs of
415 To complete page migration, we place the old and new pages back onto the LRU
417 is freed when the reference count held by the migration process is released.
426 of compaction is mostly handled by the page migration code and the same work
|
| /linux-5.19.10/tools/testing/selftests/vm/ |
| D | migration.c | 22 FIXTURE(migration) in FIXTURE() argument
31 FIXTURE_SETUP(migration) in FIXTURE_SETUP() argument
56 FIXTURE_TEARDOWN(migration) in FIXTURE_TEARDOWN() argument
114 TEST_F_TIMEOUT(migration, private_anon, 2*RUNTIME)
139 TEST_F_TIMEOUT(migration, shared_anon, 2*RUNTIME)
169 TEST_F_TIMEOUT(migration, private_anon_thp, 2*RUNTIME)
|
| D | .gitignore | 12 migration
|
| D | Makefile | 44 TEST_GEN_FILES += migration
160 $(OUTPUT)/migration: LDLIBS += -lnuma
|
| /linux-5.19.10/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-5.19.10/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-5.19.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
|
| /linux-5.19.10/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-5.19.10/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 193 migration. Postcopy live migration is one form of memory
198 migration to QEMU.
206 It is generally beneficial to run one pass of precopy live migration
207 just before starting postcopy live migration, in order to avoid
210 The implementation of postcopy live migration currently uses one
216 in the destination node, into the socket, and the migration thread of
226 by the parallel QEMU migration thread).
234 migration thread in the QEMU running in the destination node will
242 migration around and a single per-page bitmap has to be maintained in
249 postcopy thread just before ``UFFDIO_COPY|ZEROPAGE`` runs in the migration
|
| /linux-5.19.10/tools/perf/scripts/python/bin/ |
| D | sched-migration-report | 3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
|
| /linux-5.19.10/fs/proc/ |
| D | task_mmu.c | 444 bool migration) in smaps_account() argument
479 if ((page_count(page) == 1) || migration) { in smaps_account()
528 bool migration = false, young = false, dirty = false; in smaps_pte_entry() local
552 migration = true; in smaps_pte_entry()
563 smaps_account(mss, page, false, young, dirty, locked, migration); in smaps_pte_entry()
574 bool migration = false; in smaps_pmd_entry() local
583 migration = true; in smaps_pmd_entry()
599 locked, migration); in smaps_pmd_entry()
1400 bool migration = false; in pte_to_pagemap_entry() local
1422 migration = is_migration_entry(entry); in pte_to_pagemap_entry()
[all …]
|
| /linux-5.19.10/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-5.19.10/drivers/vfio/pci/mlx5/ |
| D | Kconfig | 7 This provides migration support for MLX5 devices using the VFIO
|
| /linux-5.19.10/kernel/irq/ |
| D | Makefile | 13 obj-$(CONFIG_GENERIC_PENDING_IRQ) += migration.o
|
| /linux-5.19.10/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-5.19.10/include/scsi/ |
| D | viosrp.h | 188 struct mad_migration_cap migration; member
|
| /linux-5.19.10/fs/nfs/ |
| D | Kconfig | 145 bool "NFSv4.1 client support for migration"
150 it can support NFSv4 migration.
152 The NFSv4.1 pieces of the Linux NFSv4 migration implementation are
|
| /linux-5.19.10/Documentation/trace/ |
| D | osnoise-tracer.rst | 139 …migration/8-54 [008] d... 5789.858413: thread_noise: migration/8:54 start 5789.858409300 dur…
144 two previous entries were about the migration thread running after a
|
| /linux-5.19.10/tools/perf/Documentation/ |
| D | perf-sched.txt | 55 79371.874603 [0010] migration/10[59] 3.350 0.004 0.011
149 Show migration events.
|