Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mel Gorman <mgorman@techsingularity.net>
To:     Peter Zijlstra <peterz@infradead.org>
Cc:     Ingo Molnar <mingo@kernel.org>,
        Vincent Guittot <vincent.guittot@linaro.org>,
        Valentin Schneider <valentin.schneider@arm.com>,
        Aubrey Li <aubrey.li@linux.intel.com>,
        Barry Song <song.bao.hua@hisilicon.com>,
        Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Mel Gorman <mgorman@techsingularity.net>
Subject: [PATCH 0/2] Scale wakeup granularity relative to nr_running
Date:   Mon, 20 Sep 2021 15:26:12 +0100
Message-Id: <20210920142614.4891-1-mgorman@techsingularity.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

It's unfortunate this is colliding with Plumbers but part of the
discussions are on select_idle_sibling and hackbench is a common
reference workload for evaluating select_idle_sibling. The
downside is that hackbench is sensitive to other factors much
more than the SIS cost. A major component is the value of
kernel.sched_wakeup_granularity_ns and this series tackles that
bit.

Patch 1 is minor, it was spotted while developing patch 2.

Patch 2 scales kernel.sched_wakeup_granularity_ns so allow
	tasks to avoid preemption longer when the machine
	is heavily overloaded.

-- 
2.31.1