LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Venkatesh Pallipadi <venki@google.com> To: Peter Zijlstra <peterz@infradead.org> Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org, Paul Turner <pjt@google.com>, Suresh Siddha <suresh.b.siddha@intel.com>, Mike Galbraith <efault@gmx.de>, Venkatesh Pallipadi <venki@google.com> Subject: [PATCH] sched: Resolve sd_idle and first_idle_cpu Catch-22 Date: Fri, 4 Feb 2011 12:51:28 -0800 [thread overview] Message-ID: <1296852688-1665-1-git-send-email-venki@google.com> (raw) Consider a system with { [ (A B) (C D) ] [ (E F) (G H) ] }, () denoting SMT siblings, [] cores on same socket and {} system wide Further, A, C and D are idle, B is busy and one of EFGH has excess load. With sd_idle logic, a check in rebalance_domains() converts tick based load balance requests from CPU A to busy load balance for core and above domains (lower rate of balance and higher load_idx). With first_idle_cpu logic, when CPU C or D tries to balance across domains the logic finds CPU A as first idle CPU in the group and nominates CPU A to idle balance across sockets. But, sd_idle above would not allow CPU A to do cross socket idle balance as CPU A switches its higher level balancing to busy balance. So, this can result is no cross socket balancing for extended periods. The fix here adds additional check to detect sd_idle logic in first_idle_cpu code path. We will now nominate (in order or preference): * First fully idle CPU * First semi-idle CPU * First CPU Note that this solution works fine for 2 SMT siblings case and won't be perfect in picking proper semi-idle in case of more than 2 SMT threads. The problem was found by looking at the code and schedstat output. I don't yet have any data to show impact of this on any workload. Signed-off-by: Venkatesh Pallipadi <venki@google.com> --- kernel/sched_fair.c | 41 +++++++++++++++++++++++++++++++++++++++-- 1 files changed, 39 insertions(+), 2 deletions(-) diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c index 62723a4..1790cc2 100644 --- a/kernel/sched_fair.c +++ b/kernel/sched_fair.c @@ -2603,6 +2603,37 @@ fix_small_capacity(struct sched_domain *sd, struct sched_group *group) return 0; } +/* + * Find if there is any busy CPUs in SD_SHARE_CPUPOWER domain of + * requested CPU. + * Bypass the check in case of SD_POWERSAVINGS_BALANCE on + * parent domain. In that case requested CPU can still be nominated as + * balancer for higher domains. + */ +static int is_cpupower_sharing_domain_idle(int cpu) +{ + struct sched_domain *sd; + int i; + + if (!(sysctl_sched_compat_yield & 0x4)) + return 1; + + for_each_domain(cpu, sd) { + if (!(sd->flags & SD_SHARE_CPUPOWER)) + break; + + if (test_sd_parent(sd, SD_POWERSAVINGS_BALANCE)) + return 1; + + for_each_cpu(i, sched_domain_span(sd)) { + if (!idle_cpu(i)) + return 0; + } + } + + return 1; +} + /** * update_sg_lb_stats - Update sched_group's statistics for load balancing. * @sd: The sched_domain whose statistics are to be updated. @@ -2625,6 +2656,7 @@ static inline void update_sg_lb_stats(struct sched_domain *sd, unsigned long load, max_cpu_load, min_cpu_load, max_nr_running; int i; unsigned int balance_cpu = -1, first_idle_cpu = 0; + unsigned int first_semiidle_cpu = 0; unsigned long avg_load_per_task = 0; if (local_group) @@ -2644,8 +2676,13 @@ static inline void update_sg_lb_stats(struct sched_domain *sd, /* Bias balancing toward cpus of our domain */ if (local_group) { if (idle_cpu(i) && !first_idle_cpu) { - first_idle_cpu = 1; - balance_cpu = i; + if (is_cpupower_sharing_domain_idle(i)) { + first_idle_cpu = 1; + balance_cpu = i; + } else if (!first_semiidle_cpu) { + first_semiidle_cpu = 1; + balance_cpu = i; + } } load = target_load(i, load_idx); -- 1.7.3.1
next reply other threads:[~2011-02-04 20:51 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-04 20:51 Venkatesh Pallipadi [this message] 2011-02-04 21:25 ` [PATCH] sched: Resolve sd_idle and first_idle_cpu Catch-22 - v1 Venkatesh Pallipadi 2011-02-07 13:50 ` Peter Zijlstra 2011-02-07 18:21 ` Venkatesh Pallipadi 2011-02-07 19:53 ` Suresh Siddha 2011-02-08 17:37 ` Venkatesh Pallipadi 2011-02-08 18:13 ` Misc sd_idle related fixes Venkatesh Pallipadi 2011-02-09 9:29 ` Peter Zijlstra 2011-02-10 17:24 ` Venkatesh Pallipadi 2011-02-08 18:13 ` [PATCH 1/3] sched: Resolve sd_idle and first_idle_cpu Catch-22 Venkatesh Pallipadi 2011-02-08 18:13 ` [PATCH 2/3] sched: fix_up broken SMT load balance dilation Venkatesh Pallipadi 2011-02-08 18:13 ` [PATCH 3/3] sched: newidle balance set idle_timestamp only on successful pull Venkatesh Pallipadi 2011-02-09 3:37 ` Mike Galbraith 2011-02-09 15:55 ` [PATCH] sched: Resolve sd_idle and first_idle_cpu Catch-22 - v1 Peter Zijlstra 2011-02-12 1:20 ` Suresh Siddha 2011-02-14 22:38 ` [PATCH] sched: Wholesale removal of sd_idle logic Venkatesh Pallipadi 2011-02-15 17:01 ` Vaidyanathan Srinivasan 2011-02-15 18:26 ` Venkatesh Pallipadi 2011-02-16 8:53 ` Vaidyanathan Srinivasan 2011-02-16 11:43 ` Peter Zijlstra 2011-02-16 13:50 ` [tip:sched/core] " tip-bot for Venkatesh Pallipadi 2011-02-15 9:15 ` [PATCH] sched: Resolve sd_idle and first_idle_cpu Catch-22 - v1 Peter Zijlstra 2011-02-15 19:11 ` Suresh Siddha 2011-02-18 1:05 ` Alex,Shi
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=1296852688-1665-1-git-send-email-venki@google.com \ --to=venki@google.com \ --cc=efault@gmx.de \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=peterz@infradead.org \ --cc=pjt@google.com \ --cc=suresh.b.siddha@intel.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: linkBe 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).