From: "xiaofeng.yan" <xiaofeng.yan@huawei.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Li Zefan <lizefan@huawei.com>, <mingo@redhat.com>,
<linux-kernel@vger.kernel.org>, <xiaofeng.yan2012@gmail.com>,
Juri Lelli <juri.lelli@gmail.com>
Subject: Re: [PATCH] sched/rt: overrun could happen in start_hrtick_dl
Date: Tue, 8 Jul 2014 16:41:35 +0800 [thread overview]
Message-ID: <53BBAEBF.4010107@huawei.com> (raw)
In-Reply-To: <20140708074943.GK19379@twins.programming.kicks-ass.net>
On 2014/7/8 15:49, Peter Zijlstra wrote:
> On Tue, Jul 08, 2014 at 10:51:02AM +0800, xiaofeng.yan wrote:
>> On 2014/7/8 10:40, Li Zefan wrote:
>>> On 2014/7/8 9:10, xiaofeng.yan wrote:
>>>> On 2014/7/7 16:41, Peter Zijlstra wrote:
>>>>> On Fri, Jul 04, 2014 at 12:02:21PM +0000, xiaofeng.yan wrote:
>>>>>> It could be wrong for the precision of runtime and deadline
>>>>>> when the precision is within microsecond level. For example:
>>>>>> Task runtime deadline period
>>>>>> P1 200us 500us 500us
>>>>>>
>>>>>> This case need enbale HRTICK feature by the next command
>>>>>> PC#echo "HRTICK" > /sys/kernel/debug/sched_features
>>>>>> PC#./schedtool -E -t 200000:500000 -e ./test&
>>>>>> PC#trace-cmd record -e sched_switch
>>>>> Are you actually using HRTICK ?
>>>> yes, If HRTICK is close , then all of runtime and deadline will be wrong.
>>> I think what peter meant is, do you use HRTICK in products or
>>> just use it for testing/experiment?
>>>
>> Thanks for your timely comments. In fact, We use HRTICK feature in product.
>> We need microsecond level
>> precision.
> Ah, thanks. Be advised that currently HRTICK is rather expensive. The
> cost is twofold: 1) doing all the kernel side hrtimer things and 2)
> programming clock hardware.
>
> Of course, if that's what you need, you're willing to pay the price.
>
> I'll see if I can put making it less expensive slightly higher on the
> (endless) todo list.
another fold: 3) Frequent migration :)
In fact, frequent migration lead to higher overload. In our product we
design new migration solution.
The simple description is as follow:
1 Set affinity in user space program at the beginning
2 Migrate happen per 100ms
3 Free task (runtime < dl_runtime)is migrated to free cpu (rt task
bandwidth < 65%) .
4 Busy task will run more time in a CPU by dynamic quota.
So the condition of migration depends on whether task is busy or idle or
not instead of deadline at some point.
This could not meet EDF requirement but meet our product :)
prev parent reply other threads:[~2014-07-08 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 12:02 [PATCH] sched/rt: overrun could happen in start_hrtick_dl xiaofeng.yan
2014-07-07 8:41 ` Peter Zijlstra
2014-07-08 1:10 ` xiaofeng.yan
2014-07-08 2:40 ` Li Zefan
2014-07-08 2:51 ` xiaofeng.yan
2014-07-08 7:49 ` Peter Zijlstra
2014-07-08 8:41 ` xiaofeng.yan [this message]
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=53BBAEBF.4010107@huawei.com \
--to=xiaofeng.yan@huawei.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=xiaofeng.yan2012@gmail.com \
/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