Searched refs:kswapd (Results 1 – 18 of 18) sorted by relevance
/linux/Documentation/translations/zh_CN/mm/ |
H A D | balance.rst | 23 选项的机会主义高阶分配请求中。在这种情况下,调用者可能也希望避免唤醒kswapd。 54 所附的补丁实现了第二个解决方案。它还 “修复”了两个问题:首先,在低内存条件下,kswapd 59 kswapd还需要知道它应该平衡哪些区。kswapd主要是在无法进行平衡的情况下需要的,可能 61 kswapd并不真正需要平衡高内存区,因为中断上下文并不请求高内存页。kswapd看zone 71 请求中设置了GFP_WAIT)。与此相反的是,决定唤醒kswapd以释放一些区的页。这个决定不是基于
|
/linux/Documentation/mm/ |
H A D | balance.rst | 15 the caller may also wish to avoid waking kswapd. 64 problems: first, kswapd is woken up as in 2.2 on low memory conditions 72 kswapd also needs to know about the zones it should balance. kswapd is 75 and all process contexts are sleeping. For 2.3, kswapd does not really 77 highmem pages. kswapd looks at the zone_wake_kswapd field in the zone 90 Orthogonal to this, is the decision to poke kswapd to free some zone pages.
|
H A D | multigen_lru.rst | 9 memory. It directly impacts the kswapd CPU usage and RAM efficiency.
|
/linux/Documentation/translations/zh_CN/core-api/ |
H A D | memory-allocation.rst | 86 试图从当前上下文中释放内存,但如果该区域低于低水位,可以唤醒kswapd来回收内存。可
|
/linux/Documentation/translations/zh_TW/admin-guide/mm/damon/ |
H A D | reclaim.rst | 24 有助於節省內存和減少延遲高峯,這些延遲是由直接回收進程或kswapd的CPU消耗引起的,同時只產
|
/linux/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
H A D | reclaim.rst | 24 有助于节省内存和减少延迟高峰,这些延迟是由直接回收进程或kswapd的CPU消耗引起的,同时只产
|
/linux/mm/ |
H A D | vmscan.c | 7201 static int kswapd(void *p) in kswapd() function 7374 if (!pgdat->kswapd) { in kswapd_run() 7375 pgdat->kswapd = kthread_create_on_node(kswapd, pgdat, nid, "kswapd%d", nid); in kswapd_run() 7376 if (IS_ERR(pgdat->kswapd)) { in kswapd_run() 7379 nid, PTR_ERR(pgdat->kswapd)); in kswapd_run() 7381 pgdat->kswapd = NULL; in kswapd_run() 7383 wake_up_process(pgdat->kswapd); in kswapd_run() 7396 struct task_struct *kswapd; in kswapd_stop() local 7399 kswapd = pgdat->kswapd; in kswapd_stop() 7400 if (kswapd) { in kswapd_stop() [all …]
|
H A D | compaction.c | 2193 running = pgdat->kswapd && task_is_running(pgdat->kswapd); in kswapd_is_running()
|
/linux/Documentation/admin-guide/sysctl/ |
H A D | vm.rst | 1048 This factor controls the aggressiveness of kswapd. It defines the 1049 amount of memory left in a node/system before kswapd is woken up and 1050 how much memory needs to be free before kswapd goes back to sleep. 1056 A high rate of threads entering direct reclaim (allocstall) or kswapd 1058 that the number of free pages kswapd maintains for latency reasons is 1060 can then be used to tune kswapd aggressiveness accordingly.
|
/linux/Documentation/admin-guide/mm/ |
H A D | multigen_lru.rst | 9 memory. It directly impacts the kswapd CPU usage and RAM efficiency.
|
H A D | concepts.rst | 185 allocation request will awaken the ``kswapd`` daemon. It will
|
H A D | transhuge.rst | 172 means that an application will wake kswapd in the background 180 other regions will wake kswapd in the background to reclaim
|
/linux/Documentation/core-api/ |
H A D | memory-allocation.rst | 102 context but can wake kswapd to reclaim memory if the zone is below
|
/linux/Documentation/admin-guide/mm/damon/ |
H A D | reclaim.rst | 17 reclaim of the process or CPU consumption of kswapd, while incurring only
|
/linux/Documentation/arch/x86/ |
H A D | sgx.rst | 163 Similar to the core kswapd, ksgxd, is responsible for managing the
|
/linux/fs/xfs/libxfs/ |
H A D | xfs_btree.c | 2996 bool kswapd; /* allocation in kswapd context */ member 3019 if (args->kswapd) in xfs_btree_split_worker() 3080 args.kswapd = current_is_kswapd(); in xfs_btree_split()
|
/linux/Documentation/admin-guide/ |
H A D | cgroup-v2.rst | 1565 Amount of scanned pages by kswapd (in an inactive LRU list) 1574 Amount of reclaimed pages by kswapd 1651 Number of pages demoted by kswapd.
|
/linux/ |
H A D | CREDITS | 3362 D: kswapd fixes, random kernel hacker, rmap VM,
|