From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org,
Tobias Huschle <huschle@linux.ibm.com>,
Luis Machado <luis.machado@arm.com>,
Chen Yu <yu.c.chen@intel.com>, Abel Wu <wuyun.abel@bytedance.com>,
Tianchen Ding <dtcccc@linux.alibaba.com>,
Youssef Esmat <youssefesmat@chromium.org>,
Xuewen Yan <xuewen.yan94@gmail.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [RFC PATCH 0/1] sched/eevdf: Curb wakeup preemption further
Date: Thu, 28 Mar 2024 15:56:27 +0530 [thread overview]
Message-ID: <8bce19b2-37d9-4722-ba83-0088a4c9fc6a@linux.ibm.com> (raw)
In-Reply-To: <20240325060226.1540-1-kprateek.nayak@amd.com>
Hi Prateek,
On 25/03/24 11:32, K Prateek Nayak wrote:
> Wakeup preemption problem
> =========================
>
> With the curr entity's eligibility check, a wakeup preemption is very
> likely when an entity with positive lag joins the runqueue pushing the
> avg_vruntime of the runqueue backwards, making the vruntime of the
> current entity ineligible. This leads to aggressive wakeup preemption
> which was previously guarded by wakeup_granularity_ns in legacy CFS.
Is base_slice_ns not guarding it in EEVDF?
> Below figure depicts one such aggressive preemption scenario with EEVDF:
Thanks and Regards
Madadi Vineeth Reddy
next prev parent reply other threads:[~2024-03-28 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 6:02 [RFC PATCH 0/1] sched/eevdf: Curb wakeup preemption further K Prateek Nayak
2024-03-25 6:02 ` [RFC PATCH 1/1] sched/eevdf: Skip eligibility check for current entity during wakeup preemption K Prateek Nayak
2024-03-25 15:13 ` Youssef Esmat
2024-03-26 3:06 ` K Prateek Nayak
2024-04-17 6:08 ` K Prateek Nayak
2024-04-24 15:07 ` Peter Zijlstra
2024-04-25 3:34 ` K Prateek Nayak
2024-03-28 10:26 ` Madadi Vineeth Reddy [this message]
2024-03-29 3:16 ` [RFC PATCH 0/1] sched/eevdf: Curb wakeup preemption further K Prateek Nayak
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=8bce19b2-37d9-4722-ba83-0088a4c9fc6a@linux.ibm.com \
--to=vineethr@linux.ibm.com \
--cc=20240325060226.1540-1-kprateek.nayak@amd.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=dtcccc@linux.alibaba.com \
--cc=gautham.shenoy@amd.com \
--cc=huschle@linux.ibm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.machado@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wuyun.abel@bytedance.com \
--cc=xuewen.yan94@gmail.com \
--cc=youssefesmat@chromium.org \
--cc=yu.c.chen@intel.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 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.