Re: [PATCH V5 07/17] blk-throttle: make sure expire time isn't too big
From: Tejun Heo <tj@kernel.org>
Date: 2017-01-09 19:54:19
Also in:
lkml
On Thu, Dec 15, 2016 at 12:32:58PM -0800, Shaohua Li wrote:
quoted hunk ↗ jump to hunk
cgroup could be throttled to a limit but when all cgroups cross high limit, queue enters a higher state and so the group should be throttled to a higher limit. It's possible the cgroup is sleeping because of throttle and other cgroups don't dispatch IO any more. In this case, nobody can trigger current downgrade/upgrade logic. To fix this issue, we could either set up a timer to wakeup the cgroup if other cgroups are idle or make sure this cgroup doesn't sleep too long. Setting up a timer means we must change the timer very frequently. This patch chooses the latter. Making cgroup sleep time not too big wouldn't change cgroup bps/iops, but could make it wakeup more frequently, which isn't a big issue because throtl_slice * 8 is already quite big. Signed-off-by: Shaohua Li <redacted> --- block/blk-throttle.c | 4 ++++ 1 file changed, 4 insertions(+)diff --git a/block/blk-throttle.c b/block/blk-throttle.c index 0f65fce..41ec72c 100644 --- a/block/blk-throttle.c +++ b/block/blk-throttle.c@@ -588,6 +588,10 @@ static void throtl_dequeue_tg(struct throtl_grp *tg) static void throtl_schedule_pending_timer(struct throtl_service_queue *sq, unsigned long expires) { + unsigned long max_expire = jiffies + 8 * throtl_slice; + + if (time_after(expires, max_expire)) + expires = max_expire;
A comment explaining why we need this would be nice. Thanks. -- tejun