From: Daniel Wagner <wagi@monom.org>
To: Juri Lelli <juri.lelli@arm.com>,
Daniel Wagner <daniel.wagner@bmw-carit.de>,
"juri.lelli@gmail.com" <juri.lelli@gmail.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] sched: Do not try to replenish from a non deadline tasks
Date: Fri, 10 Oct 2014 10:17:28 +0200 [thread overview]
Message-ID: <54379618.9050305@monom.org> (raw)
In-Reply-To: <543692DF.9020705@arm.com>
Good Morning Juri,
On 10/09/2014 03:51 PM, Juri Lelli wrote:
> Hi Daniel,
>
> On 09/10/14 10:47, Daniel Wagner wrote:
>> Hi Juri,
>>
>> On 10/07/2014 03:20 PM, Daniel Wagner wrote:
>>> On 10/07/2014 02:10 PM, Daniel Wagner wrote:
>>>> [ 36.689416] pthread_-1555 0d..5 18486408us : sched_stat_sleep: comm=pthread_test pid=1554 delay=143975 [ns]
>>>> [ 36.689416] pthread_-1555 0d..5 18486408us : sched_wakeup: comm=pthread_test pid=1554 prio=120 success=1 target_cpu=000
>>>> [ 36.689416] pthread_-1555 0d..4 18486420us : sched_pi_setprio: comm=pthread_test pid=1555 oldprio=-1 newprio=-1
>>>> [ 36.689416] pthread_-1555 0d..4 18486421us : sched_dequeue_dl_entity: comm=pthread_test pid=1555 flags=0
>>>> [ 36.689416] pthread_-1555 0d..4 18486421us : sched_enqueue_dl_entity: comm=pthread_test pid=1555 pi_comm=pthread_test pi_pid=1555 flags=8
>>>> [ 36.689416] pthread_-1555 0d..4 18486421us : sched_dequeue_dl_entity: comm=pthread_test pid=1555 flags=0
>>>> [ 36.689416] pthread_-1555 0d..4 18486422us : sched_enqueue_dl_entity: comm=pthread_test pid=1555 pi_comm=pthread_test pi_pid=1555 flags=0
>>>> [ 36.689416] pthread_-1555 0d.H4 18486539us : sched_enqueue_dl_entity: comm=pthread_test pid=1555 pi_comm=pthread_test pi_pid=1555 flags=8
>>>
>>> I noticed that the last two lines are different. Maybe that is yet
>>> another path into enqueue_task_dl().
>>
>> So more testing revealed that the patch also starve both task
>> eventually. Both process make no progress at all.
>>
>
> Mmm, that's bad.
>
> Can you give a try to this different patch (after applying
> the other one I sent out)?
>
> This thing is looking good on my box. I'd like to do more
> testing, but I have to context switch for a bit now :/.
I'll applied both patches and my test program runs fine since a couple
hours. Before that a panic triggered within minutes.
cheers,
daniel
next prev parent reply other threads:[~2014-10-10 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 13:24 [PATCH] sched: Do not try to replenish from a non deadline tasks Daniel Wagner
2014-10-07 9:43 ` Juri Lelli
2014-10-07 12:02 ` Daniel Wagner
2014-10-07 12:10 ` Daniel Wagner
2014-10-07 13:20 ` Daniel Wagner
2014-10-09 9:47 ` Daniel Wagner
2014-10-09 13:51 ` Juri Lelli
2014-10-10 8:17 ` Daniel Wagner [this message]
2014-10-09 13:48 ` 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=54379618.9050305@monom.org \
--to=wagi@monom.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=juri.lelli@arm.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.