[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E01B81C.2030506@jp.fujitsu.com>
Date: Wed, 22 Jun 2011 18:38:36 +0900
From: Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
To: Paul Turner <pjt@...gle.com>
CC: linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Bharata B Rao <bharata@...ux.vnet.ibm.com>,
Dhaval Giani <dhaval.giani@...il.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Srivatsa Vaddagiri <vatsa@...ibm.com>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...e.hu>, Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [patch 06/16] sched: add a timer to handle CFS bandwidth refresh
(2011/06/21 16:16), Paul Turner wrote:
> This patch adds a per-task_group timer which handles the refresh of the global
> CFS bandwidth pool.
>
> Since the RT pool is using a similar timer there's some small refactoring to
> share this support.
>
> Signed-off-by: Paul Turner <pjt@...gle.com>
> Reviewed-by: Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
>
> ---
(snip)
> @@ -413,8 +444,26 @@ static void init_cfs_rq_runtime(struct c
> cfs_rq->runtime_enabled = 0;
> }
>
> +/* requires cfs_b->lock */
> +static void __start_cfs_bandwidth(struct cfs_bandwidth *cfs_b)
> +{
> + /*
> + * Handle the extremely unlikely case of trying to start the period
> + * timer, while that timer is in the tear-down path from having
> + * decided to no longer run. In this case we must wait for the
> + * (tail of the) callback to terminate so that we can re-enqueue it.
> + */
> + if (unlikely(hrtimer_active(&cfs_b->period_timer)))
> + hrtimer_cancel(&cfs_b->period_timer);
> +
> + cfs_b->timer_active = 1;
> + start_bandwidth_timer(&cfs_b->period_timer, cfs_b->period);
> +}
> +
Nice trick :-)
(Again,)
Reviewed-by: Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Thanks,
H.Seto
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists