From: Vincent Guittot <vincent.guittot@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mel Gorman <mgorman@techsingularity.net>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Valentin Schneider <valentin.schneider@arm.com>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH 3/3] sched/numa: Limit the amount of imbalance that can exist at fork time
Date: Tue, 17 Nov 2020 15:31:19 +0100 [thread overview]
Message-ID: <CAKfTPtDQgv8RCe1RRCGg0px0Bp6GbdAhXbRKTH5zeVaRDmK+vg@mail.gmail.com> (raw)
In-Reply-To: <20201117141814.GN3121392@hirez.programming.kicks-ass.net>
On Tue, 17 Nov 2020 at 15:18, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Tue, Nov 17, 2020 at 01:42:22PM +0000, Mel Gorman wrote:
> > - if (local_sgs.idle_cpus)
> > + if (local_sgs.idle_cpus >= (sd->span_weight >> 2))
> > return NULL;
>
> Is that the same 25% ?
same question for me
could we encapsulate this 25% allowed imbalance like for adjust_numa_imbalance
next prev parent reply other threads:[~2020-11-17 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 13:42 [RFC PATCH 0/3] Revisit NUMA imbalance tolerance and fork balancing Mel Gorman
2020-11-17 13:42 ` [PATCH 1/3] sched/numa: Rename nr_running and break out the magic number Mel Gorman
2020-11-17 13:42 ` [PATCH 2/3] sched/numa: Allow a floating imbalance between NUMA nodes Mel Gorman
2020-11-17 14:16 ` Peter Zijlstra
2020-11-17 14:43 ` Mel Gorman
2020-11-17 14:24 ` Vincent Guittot
2020-11-17 14:44 ` Mel Gorman
2020-11-17 13:42 ` [PATCH 3/3] sched/numa: Limit the amount of imbalance that can exist at fork time Mel Gorman
2020-11-17 14:18 ` Peter Zijlstra
2020-11-17 14:31 ` Vincent Guittot [this message]
2020-11-17 15:17 ` Mel Gorman
2020-11-17 15:53 ` Vincent Guittot
2020-11-17 17:28 ` Mel Gorman
2020-11-18 16:06 ` Vincent Guittot
2020-11-18 16:50 ` Mel Gorman
2020-11-22 15:04 ` [sched/numa] e7f28850ea: unixbench.score 1.5% improvement kernel test robot
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=CAKfTPtDQgv8RCe1RRCGg0px0Bp6GbdAhXbRKTH5zeVaRDmK+vg@mail.gmail.com \
--to=vincent.guittot@linaro.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.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).