public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirill Tkhai <tkhai@yandex.ru>
To: Peter Zijlstra <peterz@infradead.org>,
	Mike Galbraith <bitbucket@online.de>
Cc: Juri Lelli <juri.lelli@gmail.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/rt: fix rt timer activation/deactivation
Date: Wed, 26 Feb 2014 13:35:42 +0400	[thread overview]
Message-ID: <341791393407342@web8h.yandex.ru> (raw)
In-Reply-To: <20140226090700.GG18404@twins.programming.kicks-ass.net>



26.02.2014, 13:07, "Peter Zijlstra" <peterz@infradead.org>:
> On Wed, Feb 26, 2014 at 03:37:38AM +0100, Mike Galbraith wrote:
>
>>  BTW, I noticed you can no longer turn the turn the noisy thing off since
>>  we grew DL.  I added an old SGI boot parameter to tell it to go away.
>
> You're talking about the rt badnwidth timer, right?
>
>  1) why won't it go away with DL added?

We know nothing about rt_time and rt_runtime values, when we are doing
update_curr_dl().

rt_time maybe not zero, so we increment rt_time.

rt_rq->rt_runtime maybe less than maximum available for RT(and for dl too),
because someone could borrow a part of rt_runtime during previous
balance_runtime().

If dl task uses all available runtime, we always will have "idle = 0"

        if (rt_rq->rt_time || rt_rq->rt_nr_running)
                idle = 0;

in do_sched_rt_period_timer(). Timer will be restarted.

This is boundary case, of course.

>  2) it should never appear when !rt_bandwidth_enabled(), so if you set
>  sysctl_sched_rt_runtime to -1 all this should go away already, no extra
>  patches required.

  reply	other threads:[~2014-02-26  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 16:05 [PATCH] sched/rt: fix rt timer activation/deactivation Juri Lelli
2014-02-25 20:56 ` Kirill Tkhai
2014-02-26  2:37   ` Mike Galbraith
2014-02-26  9:07     ` Peter Zijlstra
2014-02-26  9:35       ` Kirill Tkhai [this message]
2014-02-26 10:01         ` Kirill Tkhai
2014-02-26 10:02       ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=341791393407342@web8h.yandex.ru \
    --to=tkhai@yandex.ru \
    --cc=bitbucket@online.de \
    --cc=juri.lelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox