Home
last modified time | relevance | path

Searched refs:sectors_to_gc (Results 1 - 8 of 8) sorted by relevance

/kernel/linux/linux-5.10/drivers/md/bcache/
H A Dbtree.h197 atomic_set(&c->sectors_to_gc, c->cache->sb.bucket_size * c->nbuckets / 16); in set_gc_sectors()
295 * Garbage collection thread only works when sectors_to_gc < 0, in force_wake_up_gc()
296 * calling wake_up_gc() won't start gc thread if sectors_to_gc is in force_wake_up_gc()
298 * Therefore sectors_to_gc is set to -1 here, before waking up in force_wake_up_gc()
302 * that c->sectors_to_gc being set to other positive value. So in force_wake_up_gc()
306 atomic_set(&c->sectors_to_gc, -1); in force_wake_up_gc()
H A Dbcache.h653 atomic_t sectors_to_gc; member
H A Drequest.c195 if (atomic_sub_return(bio_sectors(bio), &op->c->sectors_to_gc) < 0) in bch_data_insert_start()
H A Dbtree.c1848 if (atomic_read(&c->sectors_to_gc) < 0) in gc_should_run()
/kernel/linux/linux-6.6/drivers/md/bcache/
H A Dbtree.h197 atomic_set(&c->sectors_to_gc, c->cache->sb.bucket_size * c->nbuckets / 16); in set_gc_sectors()
295 * Garbage collection thread only works when sectors_to_gc < 0, in force_wake_up_gc()
296 * calling wake_up_gc() won't start gc thread if sectors_to_gc is in force_wake_up_gc()
298 * Therefore sectors_to_gc is set to -1 here, before waking up in force_wake_up_gc()
302 * that c->sectors_to_gc being set to other positive value. So in force_wake_up_gc()
306 atomic_set(&c->sectors_to_gc, -1); in force_wake_up_gc()
H A Dbcache.h659 atomic_t sectors_to_gc; member
H A Drequest.c195 if (atomic_sub_return(bio_sectors(bio), &op->c->sectors_to_gc) < 0) in bch_data_insert_start()
H A Dbtree.c1869 if (atomic_read(&c->sectors_to_gc) < 0) in gc_should_run()

Completed in 16 milliseconds