[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d2ad284-c887-4377-9512-a74dc418efa1@linux.alibaba.com>
Date: Thu, 14 Nov 2024 15:47:09 +0800
From: Tianchen Ding <dtcccc@...ux.alibaba.com>
To: 解 咏梅 <xieym_ict@...mail.com>
Cc: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>,
Mel Gorman <mgorman@...e.de>, Valentin Schneider <vschneid@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] sched/eevdf: Force propagating min_slice of cfs_rq
when a task changing slice
On 2024/11/14 15:33, 解 咏梅 wrote:
> delayed dequeue is nessary for eevdf to maintain lag. Paw’s relative vruntime is
> not necessary any more in migration path.
>
>
> it is not a tuning option.
>
> regards,
> Yongmei
I don't know why you so focus on DELAY_DEQUEUE, it is not related to the case I
explained.
The case is about cgroup hierarchy. And the task_A in my case is already blocked
and *out of rq*
I'm talking about its enqueue path when woken up.
Powered by blists - more mailing lists