On 3/22/19 3:48 PM, Igor Konopko wrote:
In case of write recovery path, there is a chance that writer thread
is not active, so for sanity it would be good to always kick it.
Signed-off-by: Igor Konopko <igor.j.konopko@xxxxxxxxx>
Reviewed-by: Javier González <javier@xxxxxxxxxxx>
Reviewed-by: Hans Holmberg <hans.holmberg@xxxxxxxxxxxx>
---
drivers/lightnvm/pblk-write.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/lightnvm/pblk-write.c b/drivers/lightnvm/pblk-write.c
index 6593dea..4e63f9b 100644
--- a/drivers/lightnvm/pblk-write.c
+++ b/drivers/lightnvm/pblk-write.c
@@ -228,6 +228,7 @@ static void pblk_submit_rec(struct work_struct *work)
mempool_free(recovery, &pblk->rec_pool);
atomic_dec(&pblk->inflight_io);
+ pblk_write_kick(pblk);
}
Thanks Igor. I've updated the description a bit.
"In case of write recovery path, there is a chance that writer thread
is not active, kick immediately instead of waiting for timer."
