On Thu, Mar 14, 2019 at 5:08 PM Igor Konopko <igor.j.konopko@xxxxxxxxx> 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. Makes sense. Reviewed-by: Hans Holmberg <hans.holmberg@xxxxxxxxxxxx> > > Signed-off-by: Igor Konopko <igor.j.konopko@xxxxxxxxx> > --- > 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); > } > > > -- > 2.9.5 >
