Home
last modified time | relevance | path

Searched full:migration (Results 1 – 25 of 308) sorted by relevance

12345678910>>...13

/Linux-v5.4/Documentation/vm/
Dpage_migration.rst4 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 …]
Dhmm.rst25 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
Dunevictable-lru.rst79 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 …]
/Linux-v5.4/mm/
Dmigrate.c3 * Memory Migration functionality - linux/mm/migrate.c
7 * Page migration was first developed in the context of the memory hotplug
8 * project. The main authors of the migration code are:
110 * compaction threads can race against page migration functions in isolate_movable_page()
114 * being (wrongly) re-isolated while it is under migration, in isolate_movable_page()
162 * from where they were once taken off for compaction/migration.
202 * Restore a potential migration pte to a working pte entry
226 /* PMD-mapped THP migration entry */ in remove_migration_pte()
240 * Recheck VMA as permissions can change since migration started in remove_migration_pte()
286 * Get rid of all migration entries and replace them by
[all …]
DKconfig182 depends on MIGRATION
210 bool "Allow for balloon memory compaction/migration"
218 by the guest workload. Allowing the compaction & migration for memory
227 select MIGRATION
240 # support for page migration
242 config MIGRATION config
243 bool "Page migration"
247 Allows the migration of the physical location of pages of processes
251 pages as migration can relocate pages to satisfy a huge page
475 select MIGRATION
Dcompaction.c6 * this heavily depends upon page migration to do all the real heavy
127 * With it, VM migration doesn't try to put it back. in __ClearPageMovable()
290 * is necessary for the block to be a migration source/target. in __reset_isolation_pfn()
597 * so it is correct to skip the suitable migration target in isolate_freepages_block()
802 /* async migration should just abort */ in isolate_migratepages_block()
819 /* Time to isolate some pages for migration */ in isolate_migratepages_block()
824 * We have isolated all migration candidates in the in isolate_migratepages_block()
936 * Migration will fail if an anonymous page is pinned in memory, in isolate_migratepages_block()
1052 * scanning in the near future or migration failed in which case the in isolate_migratepages_block()
1142 /* Returns true if the page is within a block suitable for migration to */
[all …]
/Linux-v5.4/Documentation/admin-guide/mm/
Duserfaultfd.rst115 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
/Linux-v5.4/include/linux/
Dballoon_compaction.h7 * Balloon page migration makes use of the general non-lru movable page
11 * page->mapping is used in context of non-lru page migration to reference
12 * the address space operations for page isolation/migration/compaction.
17 * and safely perform balloon's page compaction and migration we must, always,
33 * compaction / migration.
51 * have to cope for page compaction / migration, as well as it serves the
55 unsigned long isolated_pages; /* # of isolated pages for migration */
/Linux-v5.4/Documentation/virt/kvm/devices/
Dvm.txt244 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
Dxive.txt166 It is important for migration to capture the cached IPB from the NVT
176 * Migration:
186 transferred in the migration sequence.
/Linux-v5.4/kernel/cgroup/
Dcgroup-internal.h88 /* used to track tasks and csets during migration */
103 * Before migration is committed, the target migration tasks are on
106 * or ->dst_csets depending on whether migration is committed.
116 /* migration context also tracks preloading */
120 * atomic success or failure on actual migration.
128 /* subsystems affected by migration */
/Linux-v5.4/Documentation/admin-guide/cgroup-v1/
Dmemcg_test.rst102 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.
/Linux-v5.4/tools/perf/scripts/python/bin/
Dsched-migration-report2 # description: sched migration overview
3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/sched-migration.py
/Linux-v5.4/Documentation/networking/
Dnet_failover.rst24 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
/Linux-v5.4/fs/ocfs2/dlm/
Ddlmmaster.c824 /* if there is a migration in progress, let the migration in dlm_get_lock_resource()
826 * of the MIGRATION mle: either the migrate finished or in dlm_get_lock_resource()
838 mig ? "MIGRATION" : "BLOCK"); in dlm_get_lock_resource()
1593 mlog(0, "migration mle was found (%u->%u)\n", in dlm_master_request_handler()
1826 " from %u for migration\n", in dlm_assert_master_handler()
1831 " from %u for migration, ignoring\n", in dlm_assert_master_handler()
1933 mlog(0, "finishing off migration of lockres %.*s, " in dlm_assert_master_handler()
1979 * ref given by the master / migration request message. in dlm_assert_master_handler()
2121 * prevent migration from starting while we're still asserting in dlm_assert_master_worker()
2122 * our dominance. The reserved ast delays migration. in dlm_assert_master_worker()
[all …]
/Linux-v5.4/arch/powerpc/platforms/pseries/
Dmobility.c3 * Support for Partition Mobility/Migration
407 * Used by drmgr to determine the kernel behavior of the migration interface.
409 * Version 1: Performs all PAPR requirements for migration including
414 static CLASS_ATTR_WO(migration);
427 pr_err("mobility: unable to create migration sysfs file (%d)\n", rc); in mobility_sysfs_init()
/Linux-v5.4/drivers/misc/sgi-gru/
Dgrutlbpurge.c106 * - intrablade process migration between cpus is not frequent but is
109 * blade because of intrablade migration
110 * - interblade migration is rare. Processes migrate their GRU context to
112 * - if interblade migration occurs, migration back to the original blade
/Linux-v5.4/fs/nfs/
DKconfig145 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-v5.4/Documentation/admin-guide/device-mapper/
Dcache.rst31 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
/Linux-v5.4/arch/mips/include/asm/sn/sn0/
Dhubmd.h41 #define MD_MIG_CANDIDATE 0x200040 /* Latest page migration candidate */
42 #define MD_MIG_CANDIDATE_CLR 0x200048 /* Clear page migration candidate */
384 /* Protection and migration field values */
395 #define MD_PPROT_MIGMD_SHFT 3 /* Migration mode */
408 #define MD_SPROT_MIGMD_SHFT 3 /* Migration mode */
414 /* Migration modes used in protection entries */
423 * Operations on page migration threshold register
455 * Operations on page migration count difference and absolute threshold
504 * Operations on page migration candidate register
/Linux-v5.4/drivers/md/
Ddm-cache-policy.h54 * if a migration has just been queued.
60 * Sometimes the core target can optimise a migration, eg, the
62 * In order to optimise it needs the migration immediately though
/Linux-v5.4/drivers/virtio/
Dvirtio_balloon.c687 * virtballoon_migratepage - perform the balloon page migration on behalf of
690 * @newpage: page that will replace the isolated page after migration finishes.
692 * @mode : compaction mode -- not used for balloon page migration.
695 * function that performs the page migration on behalf of a compaction thread
696 * The page migration for virtio balloon is done in a simple swap fashion which
701 * This function preforms the balloon page migration task.
714 * this turn, as it is easier to retry the page migration later. in virtballoon_migratepage()
724 /* balloon's page migration 1st step -- inflate "newpage" */ in virtballoon_migratepage()
734 /* balloon's page migration 2nd step -- deflate "page" */ in virtballoon_migratepage()
/Linux-v5.4/Documentation/trace/
Dhwlat_detector.rst81 tracing_cpumask between each window. To limit the migration, either modify
83 affinity directly, and the migration will stop.
/Linux-v5.4/Documentation/powerpc/
Ddawr-power9.rst35 migration from POWER8 to POWER9, at the cost of silently losing the
36 DAWR on the migration.
/Linux-v5.4/arch/ia64/kernel/
Dirq.c15 * 4/14/2004: Added code to handle cpu migration and do safe irq
16 * migration without losing interrupts for iosapic

12345678910>>...13