linux-kernel - [PATCH v5 0/3] sched: Limiting idle balance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1379096813-3032-1-git-send-email-jason.low2@hp.com>
Date:	Fri, 13 Sep 2013 11:26:50 -0700
From:	Jason Low <jason.low2@...com>
To:	mingo@...hat.com, peterz@...radead.org, jason.low2@...com
Cc:	linux-kernel@...r.kernel.org, efault@....de, pjt@...gle.com,
	preeti@...ux.vnet.ibm.com, akpm@...ux-foundation.org,
	mgorman@...e.de, riel@...hat.com, aswin@...com,
	scott.norton@...com, srikar@...ux.vnet.ibm.com, chegu_vinod@...com
Subject: [PATCH v5 0/3] sched: Limiting idle balance

v4->v5
- We don't use the this_rq->avg_idle < this_rq->max_idle_balance_cost check.
  However, we kept the old rq->avg_idle < sysctl_sched_migration_cost since
  I saw some performance benefits with it.
- Substitute smp_processor_id() with this_cpu.
- Increase the decay to 1% per second.

These patches modify and add to the way we limit idle balancing. The first
patch reduces the chance we overestimate the avg_idle guestimator. The second
patch makes idle balance compare the avg_idle with the max cost we ever spend
on a new idle load balance per sched domain to limit idle balance. The third
patch periodically decays each domain's max newidle balance costs.

These changes further reduce the chance we attempt idle balancing when the time
a CPU remains idle is short and is not more than the cost to do the balancing.

The table below compares the average jobs per minute when running AIM7 on
an 8 socket (80 core) machine at 10-100, 200-1000, and 1100-2000 users between
the vanilla 3.11 tip kernel and the 3.11 tip kernel with Hyperthreading enabled.
Out of the AIM7 workloads, fserver benefited most with this change.

Note: The gains weren't as large as with the v4 patch due to not having
the if (this_rq->avg_idle < this_rq->max_idle_balance_cost) check.

----------------------------------------------------------------
workload     | % improvement   | % improvement  | % improvement
             | with patch      | with patch     | with patch
             | 1100-2000 users | 200-1000 users | 10-100 users
----------------------------------------------------------------
alltests     |  +2.5%          |  +2.7%         |  +0.0%
----------------------------------------------------------------
compute      |  +0.2%          |  -0.3%         |  -0.5%
----------------------------------------------------------------
custom       |  +4.7%          |  +1.7%         |  +3.5%
----------------------------------------------------------------
disk         |  +3.0%          |  +1.9%         |  +4.8%
----------------------------------------------------------------
fserver      | +27.0%          |  +7.7%         |  +2.2%
----------------------------------------------------------------
high_systime |  +4.1%          |  +3.0%         |  +0.2%
----------------------------------------------------------------
new_fserver  | +23.1%          |  +5.1%         |  +0.0%
----------------------------------------------------------------
shared       |  +3.0%          |  +4.5%         |  +1.4%
----------------------------------------------------------------

Jason Low (3):
  sched: Reduce overestimating rq->avg_idle
  sched: Consider max cost of idle balance per sched domain
  sched: Periodically decay max cost of idle balance

 arch/metag/include/asm/topology.h |    2 +
 include/linux/sched.h             |    4 +++
 include/linux/topology.h          |    6 ++++
 kernel/sched/core.c               |   10 ++++---
 kernel/sched/fair.c               |   54 ++++++++++++++++++++++++++++++++-----
 kernel/sched/sched.h              |    3 ++
 6 files changed, 68 insertions(+), 11 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/