On 6 December 2017 at 12:38, Patrick Bellasi wrote:
> Hi Vincent,
>
> On 06-Dec 10:39, Vincent Guittot wrote:
>> Hi Patrick,
>>
>> On 30 November 2017 at 12:47, Patrick Bellasi
>> wrote:
>
> [...]
>
>> > static void dequeue_task_rt(struct rq
On 6 December 2017 at 12:38, Patrick Bellasi wrote:
> Hi Vincent,
>
> On 06-Dec 10:39, Vincent Guittot wrote:
>> Hi Patrick,
>>
>> On 30 November 2017 at 12:47, Patrick Bellasi
>> wrote:
>
> [...]
>
>> > static void dequeue_task_rt(struct rq *rq, struct task_struct *p, int
>> > flags)
>> > @@
Hi Vincent,
On 06-Dec 10:39, Vincent Guittot wrote:
> Hi Patrick,
>
> On 30 November 2017 at 12:47, Patrick Bellasi wrote:
[...]
> > static void dequeue_task_rt(struct rq *rq, struct task_struct *p, int
> > flags)
> > @@ -1564,6 +1564,9 @@ pick_next_task_rt(struct
Hi Vincent,
On 06-Dec 10:39, Vincent Guittot wrote:
> Hi Patrick,
>
> On 30 November 2017 at 12:47, Patrick Bellasi wrote:
[...]
> > static void dequeue_task_rt(struct rq *rq, struct task_struct *p, int
> > flags)
> > @@ -1564,6 +1564,9 @@ pick_next_task_rt(struct rq *rq, struct task_struct
Hi Patrick,
On 30 November 2017 at 12:47, Patrick Bellasi wrote:
> Currently schedutil updates are triggered for the RT class using a single
> call place, which is part of the rt::update_curr_rt() used in:
>
> - dequeue_task_rt:
> but it does not make sense to set the
Hi Patrick,
On 30 November 2017 at 12:47, Patrick Bellasi wrote:
> Currently schedutil updates are triggered for the RT class using a single
> call place, which is part of the rt::update_curr_rt() used in:
>
> - dequeue_task_rt:
> but it does not make sense to set the schedutil's
Hi,
On 30/11/17 11:47, Patrick Bellasi wrote:
> Currently schedutil updates are triggered for the RT class using a single
> call place, which is part of the rt::update_curr_rt() used in:
>
> - dequeue_task_rt:
> but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in
> case the
Hi,
On 30/11/17 11:47, Patrick Bellasi wrote:
> Currently schedutil updates are triggered for the RT class using a single
> call place, which is part of the rt::update_curr_rt() used in:
>
> - dequeue_task_rt:
> but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in
> case the
Currently schedutil updates are triggered for the RT class using a single
call place, which is part of the rt::update_curr_rt() used in:
- dequeue_task_rt:
but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in
case the next task should not be an RT one
- put_prev_task_rt:
Currently schedutil updates are triggered for the RT class using a single
call place, which is part of the rt::update_curr_rt() used in:
- dequeue_task_rt:
but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in
case the next task should not be an RT one
- put_prev_task_rt:
10 matches
Mail list logo