Searched refs:reclaimer (Results 1 – 6 of 6) sorted by relevance
| /openbmc/linux/fs/lockd/ |
| H A D | clntlock.c | 28 static int reclaimer(void *ptr);
218 task = kthread_run(reclaimer, host, "%s-reclaim", host->h_name); in nlmclnt_recovery()
227 reclaimer(void *ptr) in reclaimer() function
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | idle_page_tracking.rst | 106 from a process address space. To avoid interference with the reclaimer, which,
110 is set on the page. The reclaimer treats the Young flag as an extra PTE
113 Since the idle memory tracking feature is based on the memory reclaimer logic,
|
| /openbmc/qemu/docs/devel/ |
| H A D | rcu.rst | 66 Used by a reader to inform the reclaimer that the reader is
70 Used by a reader to inform the reclaimer that the reader is
101 so that the reclaimer function can fetch the ``struct foo`` address
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | whatisRCU.rst | 136 So how the heck can a reclaimer tell when a reader is done, given
166 reclaimer that the reader is entering an RCU read-side critical
180 reclaimer that the reader is exiting an RCU read-side critical
189 beginning of reclaimer code. It does this by blocking until
345 reader, updater, and reclaimer.
362 +----------------------------------->| reclaimer |
579 RCU distinction between updater, namely foo_update_a(), and reclaimer,
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | sgx.rst | 160 Page reclaimer
262 As a result, the SGX core page reclaimer doesn't support reclaiming EPC
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | vfs.rst | 998 Since it may be called by the memory reclaimer, it should not
|