Searched full:migration (Results 1 – 25 of 79) sorted by relevance
1234
| /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.
260 Migration to and from device 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
[all …]
|
| D | unevictable-lru.rst | 85 detected by folio_isolate_lru(), we would prevent their migration.
234 available to the migration subsystem.
246 put to work, without preventing the migration of mlocked pages. This is why
400 replaced with an entry that refers to the new page. Linux supports migration
403 new page is mapped in place of migration entry in a VM_LOCKED VMA. If the page
407 Note that page migration can race with mlocking or munlocking of the same page.
408 There is mostly no problem since page migration requires unmapping all PTEs of
419 To complete page migration, we place the old and new pages back onto the LRU
421 is freed when the reference count held by the migration process is released.
430 of compaction is mostly handled by the page migration code and the same work
|
| D | numa.rst | 101 attempts to minimize task migration to distant scheduling domains. However,
106 System administrators and application designers can restrict a task's migration
|
| /Documentation/ABI/testing/ |
| D | debugfs-vfio | 10 What: /sys/kernel/debug/vfio/<device>/migration
15 of vfio devices that support live migration.
16 The debugfs of each vfio device that supports live migration
19 What: /sys/kernel/debug/vfio/<device>/migration/state
23 Description: Read the live migration status of the vfio device.
24 The contents of the state file reflects the migration state
|
| 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"
|
| /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.
113 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
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
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 102 The logic is very clear. (About migration, see below)
129 7. Page Migration
162 9.3 Migration
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
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 295 the VM to another physical machine. Since we want the migration to be
304 migration. Postcopy live migration is one form of memory
309 migration to QEMU.
317 It is generally beneficial to run one pass of precopy live migration
318 just before starting postcopy live migration, in order to avoid
321 The implementation of postcopy live migration currently uses one
327 in the destination node, into the socket, and the migration thread of
337 by the parallel QEMU migration thread).
345 migration thread in the QEMU running in the destination node will
353 migration around and a single per-page bitmap has to be maintained in
[all …]
|
| /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
|
| D | io-mapping.rst | 50 migration to make the mapping code work. No caller can rely on this side
|
| /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
|
| D | xive.rst | 215 It is important for migration to capture the cached IPB from the NVT
226 * Migration:
236 transferred in the migration sequence.
|
| /Documentation/networking/device_drivers/ethernet/amd/ |
| D | pds_vfio_pci.rst | 14 The ``pds-vfio-pci`` module is a PCI driver that supports Live Migration
41 # Create single VF for Live Migration via pds_core
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-client.rst | 28 and transparent state migration, this identity string must not change
68 attribute. See `RFC3530 Section 6: Filesystem Migration and Replication`_ and
71 .. _RFC3530 Section 6\: Filesystem Migration and Replication: https://tools.ietf.org/html/rfc3530#s…
|
| /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
|
| /Documentation/arch/powerpc/ |
| D | dawr-power9.rst | 43 migration from POWER8 to POWER9, at the cost of silently losing the
44 DAWR on the migration.
|
| /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
|
| /Documentation/trace/ |
| D | osnoise-tracer.rst | 160 …migration/8-54 [008] d... 5789.858413: thread_noise: migration/8:54 start 5789.858409300 dur…
165 two previous entries were about the migration thread running after a
|
| /Documentation/arch/arm64/ |
| D | legacy_instructions.rst | 24 Uses software emulation. To aid migration of software, in this mode
|
| /Documentation/virt/kvm/x86/ |
| D | running-nested-guests.rst | 66 - Live migration of "guest hypervisors" and their nested guests, for
153 guest, or for better live migration compatibility, use a named CPU
184 Live migration with nested KVM
|
| /Documentation/networking/devlink/ |
| D | devlink-port.rst | 211 Live migration is the process of transferring a live virtual machine
215 User who want PCI VFs to be able to perform live migration need to
219 with migration support, the user can migrate the VM with this VF from one HV to a
242 - Bind VF to VFIO driver with migration support::
250 Perform live migration.
|
1234