From: Roman Kagan <rkagan@amazon.de>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
Zhang Qiao <zhangqiao22@huawei.com>,
Ben Segall <bsegall@google.com>, Waiman Long <longman@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mel Gorman <mgorman@suse.de>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
"Daniel Bristot de Oliveira" <bristot@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH v3] sched/fair: sanitize vruntime of entity being placed
Date: Mon, 27 Feb 2023 09:42:54 +0100 [thread overview]
Message-ID: <Y/xtDWYTKLutOqrM@u40bc5e070a0153.ant.amazon.com> (raw)
In-Reply-To: <CAKfTPtCDxdVEmPQf=6g7n7Y+bkozXAJT1NG92wDc_quNaDiHMg@mail.gmail.com>
On Tue, Feb 21, 2023 at 06:26:11PM +0100, Vincent Guittot wrote:
> On Tue, 21 Feb 2023 at 17:57, Roman Kagan <rkagan@amazon.de> wrote:
> > What scares me, though, is that I've got a message from the test robot
> > that this commit drammatically affected hackbench results, see the quote
> > below. I expected the commit not to affect any benchmarks.
> >
> > Any idea what could have caused this change?
>
> Hmm, It's most probably because se->exec_start is reset after a
> migration and the condition becomes true for newly migrated task
> whereas its vruntime should be after min_vruntime.
>
> We have missed this condition
Makes sense to me.
But what would then be the reliable way to detect a sched_entity which
has slept for long and risks overflowing in .vruntime comparison?
Thanks,
Roman.
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next prev parent reply other threads:[~2023-02-27 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 19:31 [PATCH v3] sched/fair: sanitize vruntime of entity being placed Roman Kagan
2023-02-21 9:38 ` Vincent Guittot
2023-02-21 16:57 ` Roman Kagan
2023-02-21 17:26 ` Vincent Guittot
2023-02-27 8:42 ` Roman Kagan [this message]
2023-02-27 14:37 ` Vincent Guittot
2023-02-27 17:00 ` Dietmar Eggemann
2023-02-27 17:15 ` Vincent Guittot
2023-03-02 9:36 ` Zhang Qiao
2023-03-02 13:34 ` Vincent Guittot
2023-03-02 14:29 ` Zhang Qiao
2023-03-02 14:55 ` Vincent Guittot
2023-03-03 6:51 ` Zhang Qiao
2023-03-03 8:32 ` Vincent Guittot
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=Y/xtDWYTKLutOqrM@u40bc5e070a0153.ant.amazon.com \
--to=rkagan@amazon.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.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=zhangqiao22@huawei.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;
as well as URLs for NNTP newsgroup(s).