| /linux/Documentation/vm/ |
| A D | page_migration.rst | 4 Page migration
7 Page migration allows moving the physical location of pages between
33 Manual migration is useful if for example the scheduler has relocated
37 manual page migration support. Automatic page migration may be implemented
58 Processes will run with similar performance after migration.
60 Page migration occurs in several steps. First a high level
74 so that it cannot vanish while the page migration occurs.
83 to do the migration. It will call the function to allocate
108 or wait for the migration page table entry to be removed.
152 Non-LRU page migration
[all …]
|
| A D | hmm.rst | 25 Finally, the last section presents a new migration helper that allows
106 Shared address space and migration
130 memory for the device memory and second to perform migration. Policy decisions
136 address A triggers a page fault and initiates a migration back to main memory.
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
378 This step is where the migration is actually "committed".
389 migration on the CPU side.
400 This step replaces the special migration page table entry with the new
[all …]
|
| A D | arch_pgtable_helpers.rst | 249 | is_migration_entry | Tests a migration (read or write) swapped entry |
251 | is_write_migration_entry | Tests a write migration swapped entry |
253 | make_migration_entry_read | Converts into read migration swapped entry |
255 | make_migration_entry | Creates a migration swapped entry (read or write)|
|
| A D | unevictable-lru.rst | 79 migration, unless we reworked migration code to find the unevictable pages
233 link field was not available to the migration subsystem.
412 replaced with an entry that refers to the new page. Linux supports migration
416 Note that page migration can race with mlocking or munlocking of the same page.
418 sections above. Both processes (migration and m[un]locking) hold the page
419 locked. This provides the first level of synchronization. Page migration
423 To complete page migration, we place the new and old pages back onto the LRU
425 page on failure - will be freed when the reference count held by the migration
427 list because of a race between munlock and migration, page migration uses the
438 the page migration code and the same work flow as described in MIGRATING
[all …]
|
| /linux/Documentation/ABI/testing/ |
| A 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
|
| A 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"
|
| A D | sysfs-class-rnbd-server | 50 Description: Contains the device access mode: ro, rw or migration.
|
| /linux/Documentation/virt/kvm/devices/ |
| A 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
|
| A D | xive.rst | 215 It is important for migration to capture the cached IPB from the NVT
236 transferred in the migration sequence.
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| A 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.
|
| A 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/Documentation/admin-guide/mm/ |
| A 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/Documentation/networking/ |
| A D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with
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
|
| A D | failover.rst | 17 datapath. It also allows live migration of VMs with direct attached VFs by
|
| /linux/tools/perf/scripts/python/bin/ |
| A D | sched-migration-report | 3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
|
| /linux/kernel/irq/ |
| A D | Makefile | 13 obj-$(CONFIG_GENERIC_PENDING_IRQ) += migration.o
|
| /linux/Documentation/powerpc/ |
| A D | dawr-power9.rst | 35 migration from POWER8 to POWER9, at the cost of silently losing the
36 DAWR on the migration.
|
| /linux/fs/nfs/ |
| A 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/Documentation/trace/ |
| A 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/tools/perf/Documentation/ |
| A D | perf-sched.txt | 55 79371.874603 [0010] migration/10[59] 3.350 0.004 0.011
149 Show migration events.
|
| /linux/include/scsi/ |
| A D | viosrp.h | 183 struct mad_migration_cap migration; member
|
| /linux/Documentation/virt/kvm/ |
| A D | amd-memory-encryption.rst | 355 After completion of the migration flow, the KVM_SEV_SEND_FINISH command can be
364 SEND_CANCEL command to stop a migration. This is necessary so that a cancelled
365 migration can restart with a new target later.
425 After completion of the migration flow, the KVM_SEV_RECEIVE_FINISH command can be
|
| A D | running-nested-guests.rst | 64 - Live migration of "guest hypervisors" and their nested guests, for
151 gues); or for better live migration compatibility, use a named CPU
182 Live migration with nested KVM
|
| /linux/Documentation/admin-guide/nfs/ |
| A D | nfs-client.rst | 28 and transparent state migration, this identity string must not change
42 or loss of state during NFS reboot recovery or transparent state migration.
|
| /linux/Documentation/arm64/ |
| A D | legacy_instructions.rst | 24 Uses software emulation. To aid migration of software, in this mode
|