Home
last modified time | relevance | path

Searched refs:reaping (Results 1 – 6 of 6) sorted by relevance

/linux-6.12.1/drivers/md/dm-vdo/ !
Drecovery-journal.c348 journal->reaping || in check_for_drain_complete()
469 journal->reaping = false; in finish_reaping()
500 journal->reaping = false; in handle_flush_error()
1500 if (journal->reaping) { in reap_recovery_journal()
1544 journal->reaping = true; in reap_recovery_journal()
Drecovery-journal.h163 bool reaping; member
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/altera/ !
Daltera_tse.rst96 interrupt by obtaining the DMA receive logic status, reaping receive
/linux-6.12.1/Documentation/filesystems/xfs/ !
Dxfs-online-fsck-design.rst2459 EFIs have a role to play during the commit and reaping phases; please see the
2460 next section and the section about :ref:`reaping<reaping>` for more details.
2564 Repair moves on to reaping the old blocks, which will be presented in a
2565 subsequent :ref:`section<reaping>` after a few case studies of bulk loading.
2779 structures in the discovered free space and avoid the question of reaping.
2833 Transactions are of finite size, so the reaping process must be careful to roll
2841 This is also a window in which a crash during the reaping process can leak
2869 old data structures and hence is a candidate for reaping.
2965 The list of candidate reaping blocks is computed by setting the bits
3872 There is a downside to the reaping process -- if the system crashes during the
[all …]
/linux-6.12.1/Documentation/filesystems/caching/ !
Dcachefiles.rst41 reaping stale nodes and culling. This is called cachefilesd and lives in
/linux-6.12.1/Documentation/admin-guide/sysctl/ !
Dkernel.rst201 collecting process can block the reaping of a crashed process simply