linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
	mingo@kernel.org, vincent.guittot@linaro.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	mgorman@suse.de, bristot@redhat.com, corbet@lwn.net,
	kprateek.nayak@amd.com, youssefesmat@chromium.org,
	joel@joelfernandes.org
Subject: Re: [PATCH 00/17] sched: EEVDF using latency-nice
Date: Tue, 11 Apr 2023 21:33:33 +0800	[thread overview]
Message-ID: <20230411133333.1790-1-hdanton@sina.com> (raw)
In-Reply-To: <c66114c4b659fc0ef50c7df1769f3acadc08fd63.camel@gmx.de>

On Tue, 11 Apr 2023 12:15:41 +0200 Mike Galbraith <efault@gmx.de>
> On Mon, 2023-04-10 at 16:23 +0800, Hillf Danton wrote:
> >
> > In order to only narrow down the poor performance reported, make a tradeoff
> > between runtime and latency simply by restoring sysctl_sched_min_granularity
> > at tick preempt, given the known order on the runqueue.
> 
> Tick preemption isn't the primary contributor to the scheduling delta,
> it's wakeup preemption. If you look at the perf summaries of 5 minute
> recordings on my little 8 rq box below, you'll see that the delta is
> more than twice what a 250Hz tick could inflict.  You could also just
> turn off WAKEUP_PREEMPTION and watch the delta instantly peg negative.
> 
> Anyway...
> 
> Given we know preemption is markedly up, and as always a source of pain
> (as well as gain), perhaps we can try to tamp it down a little without
> inserting old constraints into the shiny new scheduler.
> 
> The dirt simple tweak below puts a dent in the sting by merely sticking
> with whatever decision EEVDF last made until it itself invalidates that
> decision. It still selects via the same math, just does so the tiniest
> bit less frenetically.
> 
> ---
>  kernel/sched/fair.c     |    3 +++
>  kernel/sched/features.h |    6 ++++++
>  2 files changed, 9 insertions(+)
> 
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -950,6 +950,9 @@ static struct sched_entity *pick_eevdf(s
>  	if (curr && (!curr->on_rq || !entity_eligible(cfs_rq, curr)))
>  		curr =3D NULL;
> 
> +	if (sched_feat(GENTLE_EEVDF) && curr)
> +		return curr;
> +

This is rather aggressive, given latency-10 curr and latency-0 candidate
at tick hit for instance. And along your direction a mild change is
postpone the preempt wakeup to the next tick.

+++ b/kernel/sched/fair.c
@@ -7932,8 +7932,6 @@ static void check_preempt_wakeup(struct
 		return;
 
 	cfs_rq = cfs_rq_of(se);
-	update_curr(cfs_rq);
-
 	/*
 	 * XXX pick_eevdf(cfs_rq) != se ?
 	 */


  reply	other threads:[~2023-04-11 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230328092622.062917921@infradead.org>
     [not found] ` <20230328110354.641979416@infradead.org>
2023-03-30  7:53   ` [PATCH 15/17] [RFC] sched/eevdf: Sleeper bonus Hillf Danton
     [not found] ` <20230328110354.141543852@infradead.org>
2023-03-30 11:02   ` [PATCH 08/17] sched/fair: Implement an EEVDF like policy Hillf Danton
     [not found] ` <20230328110354.562078801@infradead.org>
     [not found]   ` <CAKfTPtAkFBw5zt0+WK7dWBUE9OrbOOExG8ueUE6ogdCEQZhpXQ@mail.gmail.com>
2023-04-01 23:23     ` [PATCH 14/17] sched/eevdf: Better handle mixed slice length Hillf Danton
2023-04-02  2:40       ` Mike Galbraith
2023-04-02  6:28         ` Hillf Danton
     [not found] ` <20230410031350.GA49280@maniforge>
2023-04-10  8:23   ` [PATCH 00/17] sched: EEVDF using latency-nice Hillf Danton
2023-04-11 10:15     ` Mike Galbraith
2023-04-11 13:33       ` Hillf Danton [this message]
2023-04-11 14:56         ` Mike Galbraith
     [not found]         ` <20230412025042.1413-1-hdanton@sina.com>
2023-04-12  4:05           ` Mike Galbraith

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=20230411133333.1790-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=bristot@redhat.com \
    --cc=corbet@lwn.net \
    --cc=efault@gmx.de \
    --cc=joel@joelfernandes.org \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.org \
    --cc=youssefesmat@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox