Home
last modified time | relevance | path

Searched refs:reclaim (Results 1 – 25 of 109) sorted by relevance

12345

/linux-6.12.1/tools/testing/selftests/cgroup/
Dmemcg_protection.m5 % This script simulates reclaim protection behavior on a single level of memcg
10 % reclaim) and then the reclaim starts, all memory is reclaimable, i.e. treated
11 % same. It simulates only non-low reclaim and assumes all memory.min = 0.
27 % Minimal reclaim amount (GB)
72 % nothing to reclaim, reached equilibrium
79 % XXX here I do parallel reclaim of all siblings
80 % in reality reclaim is serialized and each sibling recalculates own residual
/linux-6.12.1/Documentation/core-api/
Dgfp_mask-from-fs-io.rst15 memory reclaim calling back into the FS or IO paths and blocking on
25 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory
26 reclaim issues.
44 any critical section with respect to the reclaim is started - e.g.
45 lock shared with the reclaim context or when a transaction context
46 nesting would be possible via reclaim. The restore function should be
48 explanation what is the reclaim context for easier maintenance.
Dmemory-allocation.rst43 direct reclaim may be triggered under memory pressure; the calling
46 handler, use ``GFP_NOWAIT``. This flag prevents direct reclaim and
75 prevent recursion deadlocks caused by direct memory reclaim calling
88 GFP flags and reclaim behavior
90 Memory allocations may trigger direct or background reclaim and it is
96 doesn't kick the background reclaim. Should be used carefully because it
98 reclaim.
102 context but can wake kswapd to reclaim memory if the zone is below
112 * ``GFP_KERNEL`` - both background and direct reclaim are allowed and the
120 reclaim (one round of reclaim in this implementation). The OOM killer
[all …]
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-kernel-mm-numa9 Description: Enable/disable demoting pages during reclaim
11 Page migration during reclaim is intended for systems
16 Allowing page migration during reclaim enables these
/linux-6.12.1/Documentation/mm/
Dmultigen_lru.rst7 page reclaim and improves performance under memory pressure. Page
8 reclaim decides the kernel's caching policy and ability to overcommit
110 eviction. They form a closed-loop system, i.e., the page reclaim.
174 ignored when the current memcg is under reclaim. Similarly, page table
175 walkers will ignore pages from nodes other than the one under reclaim.
187 can incur the highest CPU cost in the reclaim path.
228 global reclaim, which is critical to system-wide memory overcommit in
229 data centers. Note that memcg LRU only applies to global reclaim.
241 In terms of global reclaim, it has two distinct features:
245 2. Eventual fairness, which allows direct reclaim to bail out at will
[all …]
Dphysical_memory.rst280 Workqueues used to synchronize memory reclaim tasks
286 Number of pages written while reclaim is throttled waiting for writeback.
289 Controls the order kswapd tries to reclaim
295 Number of runs kswapd was unable to reclaim any pages
307 Flags controlling reclaim behavior.
/linux-6.12.1/Documentation/admin-guide/device-mapper/
Ddm-zoned.rst27 internally for storing metadata and performing reclaim operations.
108 situation, a reclaim process regularly scans used conventional zones and
109 tries to reclaim the least recently used zones by copying the valid
128 (for both incoming BIO processing and reclaim process) and all dirty
184 Normally the reclaim process will be started once there are less than 50
185 percent free random zones. In order to start the reclaim process manually
191 dmsetup message /dev/dm-X 0 reclaim
193 will start the reclaim process and random zones will be moved to sequential
/linux-6.12.1/Documentation/admin-guide/mm/
Dmultigen_lru.rst7 page reclaim and improves performance under memory pressure. Page
8 reclaim decides the kernel's caching policy and ability to overcommit
138 Proactive reclaim
140 Proactive reclaim induces page reclaim when there is no memory
142 comes in, the job scheduler wants to proactively reclaim cold pages on
/linux-6.12.1/arch/x86/kernel/cpu/sgx/
Dencl.h119 struct sgx_epc_page *sgx_alloc_va_page(bool reclaim);
126 struct sgx_va_page *sgx_encl_grow(struct sgx_encl *encl, bool reclaim);
Dsgx.h92 struct sgx_epc_page *sgx_alloc_epc_page(void *owner, bool reclaim);
/linux-6.12.1/Documentation/translations/zh_TW/admin-guide/mm/damon/
Dindex.rst24 reclaim
/linux-6.12.1/Documentation/translations/zh_CN/admin-guide/mm/damon/
Dindex.rst24 reclaim
/linux-6.12.1/Documentation/admin-guide/mm/damon/
Dindex.rst16 reclaim
/linux-6.12.1/mm/damon/
DMakefile8 obj-$(CONFIG_DAMON_RECLAIM) += modules-common.o reclaim.o
DKconfig105 bool "Build DAMON-based reclaim (DAMON_RECLAIM)"
109 that not accessed for a long time (cold) using DAMON and reclaim
/linux-6.12.1/Documentation/admin-guide/sysctl/
Dvm.rst313 reclaim to satisfy a high-order allocation. The extfrag/extfrag_index file in
541 A percentage of the total pages in each zone. On Zone reclaim
545 systems that rarely perform global reclaim.
549 Note that slab reclaim is triggered in a per zone / node fashion.
559 This is a percentage of the total pages in each zone. Zone reclaim will
1008 This percentage value controls the tendency of the kernel to reclaim
1012 reclaim dentries and inodes at a "fair" rate with respect to pagecache and
1013 swapcache reclaim. Decreasing vfs_cache_pressure causes the kernel to prefer
1015 never reclaim dentries and inodes due to memory pressure and this can easily
1017 causes the kernel to prefer to reclaim dentries and inodes.
[all …]
/linux-6.12.1/tools/testing/selftests/damon/
DMakefile17 TEST_PROGS += reclaim.sh lru_sort.sh
/linux-6.12.1/drivers/usb/host/
Doxu210hp-hcd.c307 struct ehci_qh *reclaim; /* next to reclaim */ member
399 struct ehci_qh *reclaim; member
2059 struct ehci_qh *qh = oxu->reclaim; in end_unlink_async()
2069 next = qh->reclaim; in end_unlink_async()
2070 oxu->reclaim = next; in end_unlink_async()
2072 qh->reclaim = NULL; in end_unlink_async()
2091 oxu->reclaim = NULL; in end_unlink_async()
2106 BUG_ON(oxu->reclaim || (qh->qh_state != QH_STATE_LINKED in start_unlink_async()
2114 && !oxu->reclaim) { in start_unlink_async()
2125 oxu->reclaim = qh = qh_get(qh); in start_unlink_async()
[all …]
/linux-6.12.1/drivers/md/
Ddm-zoned-target.c422 dmz_reclaim_bio_acc(zone->dev->reclaim); in dmz_handle_bio()
927 ret = dmz_ctr_reclaim(dmz->metadata, &dmz->dev[i].reclaim, i); in dmz_ctr()
969 dmz_dtr_reclaim(dmz->dev[i].reclaim); in dmz_dtr()
1041 dmz_suspend_reclaim(dmz->dev[i].reclaim); in dmz_suspend()
1055 dmz_resume_reclaim(dmz->dev[i].reclaim); in dmz_resume()
1132 dmz_schedule_reclaim(dmz->dev[i].reclaim); in dmz_message()
Ddm-zoned.h57 struct dmz_reclaim *reclaim; member
291 dmz_reclaim_bio_acc(zone->dev->reclaim); in dmz_deactivate_zone()
/linux-6.12.1/drivers/media/mmc/siano/
Dsmssdio.c303 goto reclaim; in smssdio_probe()
307 reclaim: in smssdio_probe()
/linux-6.12.1/Documentation/accounting/
Dtaskstats-struct.rst38 6) Extended delay accounting fields for memory reclaim
191 6) Extended delay accounting fields for memory reclaim::
193 /* Delay waiting for memory reclaim */
/linux-6.12.1/Documentation/admin-guide/cgroup-v1/
Dmemory.rst87 memory.force_empty trigger forced page reclaim
204 charged is over its limit. If it is, then reclaim is invoked on the cgroup.
205 More details can be found in the reclaim section of this document.
293 to reclaim memory from the cgroup so as to make space for the new
294 pages that the cgroup has touched. If the reclaim is unsuccessful,
298 The reclaim algorithm has not been modified for cgroups, except that
350 to trigger slab reclaim when those limits are reached.
398 In the current implementation, memory reclaim will NOT be triggered for
403 Since kmem charges will also be fed to the user counter and reclaim will be
628 Please note that unlike during the global reclaim, limit reclaim
[all …]
/linux-6.12.1/fs/bcachefs/
Dalloc_types.h32 x(reclaim) \
/linux-6.12.1/include/linux/lockd/
Dxdr.h69 u32 reclaim; member

12345