Re: [PATCH] cpuidle: Select polling interval based on a c-state with a longer target residency

On Tue, Dec 01, 2020 at 04:08:02PM +0100, Rafael J. Wysocki wrote: > > > Also this is about certain drivers only which support the "polling > > > idle state" (the ACPI one and intel_idle only AFAICS). So I'm not > > > sure about the framework-level tunable here. > > > > > > Moreover, to be

Re: [PATCH] cpuidle: Select polling interval based on a c-state with a longer target residency

On Mon, Nov 30, 2020 at 11:32 PM Mel Gorman wrote: > > On Mon, Nov 30, 2020 at 08:06:44PM +0100, Rafael J. Wysocki wrote: > > > diff --git a/Documentation/admin-guide/kernel-parameters.txt > > > b/Documentation/admin-guide/kernel-parameters.txt > > > index 526d65d8573a..5b8545022564 100644 > > >

Re: [PATCH] cpuidle: Select polling interval based on a c-state with a longer target residency

On Mon, Nov 30, 2020 at 08:06:44PM +0100, Rafael J. Wysocki wrote: > > diff --git a/Documentation/admin-guide/kernel-parameters.txt > > b/Documentation/admin-guide/kernel-parameters.txt > > index 526d65d8573a..5b8545022564 100644 > > --- a/Documentation/admin-guide/kernel-parameters.txt > > +++

Re: [PATCH] cpuidle: Select polling interval based on a c-state with a longer target residency

On Mon, Nov 30, 2020 at 10:22 AM Mel Gorman wrote: > > It was noted that a few workloads that idle rapidly regressed when commit > 36fcb4292473 ("cpuidle: use first valid target residency as poll time") > was merged. The workloads in question were heavy communicators that idle > rapidly and were

[PATCH] cpuidle: Select polling interval based on a c-state with a longer target residency

It was noted that a few workloads that idle rapidly regressed when commit 36fcb4292473 ("cpuidle: use first valid target residency as poll time") was merged. The workloads in question were heavy communicators that idle rapidly and were impacted by the c-state exit latency as the active CPUs were