361d889f83
pblk's recovery path is single threaded and therefore a number of assumptions regarding concurrency can be made. To avoid confusion, make this explicit with a couple of comments in the code. Signed-off-by: Javier González <javier@cnexlabs.com> Signed-off-by: Matias Bjørling <mb@lightnvm.io> Signed-off-by: Jens Axboe <axboe@kernel.dk> |
||
|---|---|---|
| .. | ||
| core.c | ||
| Kconfig | ||
| Makefile | ||
| pblk-cache.c | ||
| pblk-core.c | ||
| pblk-gc.c | ||
| pblk-init.c | ||
| pblk-map.c | ||
| pblk-rb.c | ||
| pblk-read.c | ||
| pblk-recovery.c | ||
| pblk-rl.c | ||
| pblk-sysfs.c | ||
| pblk-trace.h | ||
| pblk-write.c | ||
| pblk.h | ||