dm cache policy smq: make the cleaner policy write-back more aggressively
By ignoring the sentinels the cleaner policy is able to write-back dirty cache data much faster. There is no reason to respect the sentinels, which denote that a block was changed recently, when using the cleaner policy given that the cleaner is tasked with writing back all dirty data. Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
This commit is contained in:
parent
449b668ce0
commit
cc7e394024
|
@ -1166,7 +1166,7 @@ static void queue_writeback(struct smq_policy *mq)
|
|||
struct policy_work work;
|
||||
struct entry *e;
|
||||
|
||||
e = q_peek(&mq->dirty, mq->dirty.nr_levels, false);
|
||||
e = q_peek(&mq->dirty, mq->dirty.nr_levels, !mq->migrations_allowed);
|
||||
if (e) {
|
||||
mark_pending(mq, e);
|
||||
q_del(&mq->dirty, e);
|
||||
|
|
Loading…
Reference in New Issue