Searched full:migration (Results 1 – 25 of 48) sorted by relevance
12
| /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
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.
338 Migration to and from device memory
341 Because the CPU cannot access device memory, migration must use the device DMA
364 simplify migration to and from device memory. This also means that migration
|
| D | unevictable-lru.rst | 79 migration, unless we reworked migration code to find the unevictable pages
239 link field was not available to the migration subsystem.
418 replaced with an entry that refers to the new page. Linux supports migration
422 Note that page migration can race with mlocking or munlocking of the same page.
424 sections above. Both processes (migration and m[un]locking) hold the page
425 locked. This provides the first level of synchronization. Page migration
429 To complete page migration, we place the new and old pages back onto the LRU
431 page on failure - will be freed when the reference count held by the migration
433 list because of a race between munlock and migration, page migration uses the
444 the page migration code and the same work flow as described in MIGRATING
[all …]
|
| D | numa.rst | 103 attempts to minimize task migration to distant scheduling domains. However,
108 System administrators and application designers can restrict a task's migration
|
| D | ksm.rst | 64 NUMA balancing and page migration.
|
| /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
|
| D | memory-hotplug.rst | 106 - Page Migration (``CONFIG_MIGRATION``)
334 all pages in the memory block by page migration. But not all pages are
336 page caches. For offlining a memory block by migration, the kernel has to
442 - support HugeTLB page migration and offlining.
|
| /Documentation/virt/kvm/devices/ |
| D | vm.txt | 244 Allows userspace to stop migration mode, needed for PGSTE migration.
245 Setting this attribute when migration mode is not active will have no
253 Allows userspace to start migration mode, needed for PGSTE migration.
254 Setting this attribute when migration mode is already active will have
258 Returns: -ENOMEM if there is not enough free memory to start migration mode
264 Allows userspace to query the status of migration mode.
267 the data itself is either 0 if migration mode is disabled or 1
|
| D | xive.txt | 166 It is important for migration to capture the cached IPB from the NVT
176 * Migration:
186 transferred in the migration sequence.
|
| /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.
|
| 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
|
| D | memory.rst | 208 At page migration, accounting information is kept.
484 4.2 Task migration
492 You can move charges of a task along with task migration.
493 See 8. "Move charges at task migration"
748 8. Move charges at task migration
751 Users can move charges associated with a task along with task migration, that
774 try to make space by reclaiming memory. Task migration may fail if we
865 * move some tasks to other group with account migration.
|
| /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
|
| D | failover.rst | 17 datapath. It also allows live migration of VMs with direct attached VFs by
|
| /Documentation/powerpc/ |
| D | dawr-power9.rst | 35 migration from POWER8 to POWER9, at the cost of silently losing the
36 DAWR on the migration.
|
| D | transactional_memory.rst | 245 Guest migration from POWER8 to POWER9 will work with POWER9N DD2.2 and
247 emulation, migration from POWER8 to POWER9 is not supported there.
|
| /Documentation/trace/ |
| D | hwlat_detector.rst | 81 tracing_cpumask between each window. To limit the migration, either modify
83 affinity directly, and the migration will stop.
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache.rst | 31 Migration
35 Migration from slow device to fast device.
37 Migration from fast device to slow device.
118 Migration throttling
123 migration occurring at any one time. Currently we're not taking any
165 We can avoid copying data during migration if we know the block has
|
| D | cache-policies.rst | 12 The policy can return a simple HIT or MISS or issue a migration.
|
| /Documentation/filesystems/nfs/ |
| D | nfs.txt | 25 and transparent state migration, this identity string must not change
39 or loss of state during NFS reboot recovery or transparent state migration.
|
| /Documentation/arm64/ |
| D | legacy_instructions.rst | 24 Uses software emulation. To aid migration of software, in this mode
|
| /Documentation/virt/kvm/arm/ |
| D | psci.txt | 12 a migration causes a different PSCI version to be exposed out of the
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 19 and migration of secure software.
|
| /Documentation/virt/kvm/ |
| D | nested-vmx.txt | 74 of this structure changes, this can break live migration across KVM versions.
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 32 forward progress (NOTE: the migration thread and kstopmachine both
|
12