From: Kirill Tkhai <tkhai@yandex.ru>
To: Juri Lelli <juri.lelli@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC] sched/deadline: Prevent rt_time growth to infinity
Date: Fri, 21 Feb 2014 18:25:02 +0400 [thread overview]
Message-ID: <3231392992702@web26m.yandex.ru> (raw)
In-Reply-To: <20140221134438.ab2d02c4165fa2a6cbd663be@gmail.com>
21.02.2014, 16:44, "Juri Lelli" <juri.lelli@gmail.com>:
> On Fri, 21 Feb 2014 16:09:25 +0400
> Kirill Tkhai <tkhai@yandex.ru> wrote:
>
>> 21.02.2014, 15:39, "Kirill Tkhai" <tkhai@yandex.ru>:
>>> 21.02.2014, 14:37, "Peter Zijlstra" <peterz@infradead.org>:
>>>> On Thu, Feb 20, 2014 at 02:16:00AM +0400, Kirill Tkhai wrote:
>>>>> Since deadline tasks share rt bandwidth, we must care about
>>>>> bandwidth timer set. Otherwise rt_time may grow up to infinity
>>>>> in update_curr_dl(), if there are no other available RT tasks
>>>>> on top level bandwidth.
>>>>>
>>>>> I'm going to decide the problem the way below. Almost untested
>>>>> because of I skipped almost all of recent patches which haveto be applied from lkml.
>>>>>
>>>>> Please say, if I skipped anything in idea. Maybe better put
>>>>> start_top_rt_bandwidth() into set_curr_task_dl()?
>>>> How about we only increment rt_time when there's an RT bandwidth timer
>>>> active?
>>> This case RT and DL may eat all the time:
>>>
>>> -------------- time ------------------>
>>> |RT's working |DL's working|
>>> ----------------------------
>>> |rt_runtime | |
>>> ----------------------------
>>> | rt_period |
>>>
>>> Or at least more, than it's allowed.
>>>
>>> It looks like, if we want to limit time of high priority classes
>>> execution, we have to set the timer anyway.
>> Oh, above is confusing. Sorry.
>>
>> I mean one RT task and
>>
>> ----------------- time -------------------------->
>> |DL's working |RT's working| |DL's working |
>> --------------------------------------------------
>> | |rt_runtime | | |
>> --------------------------------------------------
>> | | rt_period | |
>>
>> In this case FAIR receives less ratio, than (rt_period-rt_runtime)/rt_period.
>
> DL tasks won't be allowed to run in this situation, as their bw exceedes
> rt_runtime/rt_period.
Maybe, I don't uderstand. Where does DL control summary (DL+RT) runtime?
RT does not do this too. But it looks like, RT has to do this.
Kirill
next prev parent reply other threads:[~2014-02-21 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 22:16 [RFC] sched/deadline: Prevent rt_time growth to infinity Kirill Tkhai
2014-02-20 21:22 ` Steven Rostedt
2014-02-21 10:37 ` Peter Zijlstra
2014-02-21 11:33 ` Kirill Tkhai
2014-02-21 12:09 ` Kirill Tkhai
2014-02-21 12:44 ` Juri Lelli
2014-02-21 14:25 ` Kirill Tkhai [this message]
2014-02-21 16:36 ` Juri Lelli
2014-02-21 16:53 ` Juri Lelli
2014-02-21 23:50 ` Kirill Tkhai
2014-02-22 0:56 ` Kirill Tkhai
2014-02-25 14:15 ` Juri Lelli
2014-02-25 14:58 ` Kirill Tkhai
2014-02-27 13:32 ` [tip:sched/urgent] " tip-bot for Juri Lelli
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=3231392992702@web26m.yandex.ru \
--to=tkhai@yandex.ru \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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