linux-kernel - [PATCH v2 0/3] Disable sched_numa

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1439290813-6683-1-git-send-email-srikar@linux.vnet.ibm.com>
Date:	Tue, 11 Aug 2015 16:30:10 +0530
From:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, srikar@...ux.vnet.ibm.com,
	Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>
Subject: [PATCH v2 0/3] Disable sched_numa_balancing on uma systems

With recent commit 2a1ed24 ("sched/numa: Prefer NUMA hotness over cache
hotness") sets sched feature NUMA to true. This can enable numa hinting
faults on a uma system.

This patchset ensures that numa hinting faults occur only on a numa system
by setting/resetting sched_numa_balancing.

This patchset
- Renames numabalancing_enabled to sched_numa_balancing
- Makes sched_numa_balancing common to CONFIG_SCHED_DEBUG and
  !CONFIG_SCHED_DEBUG. Earlier it was only in !CONFIG_SCHED_DEBUG
- Checks for sched_numa_balancing instead of sched_feat(NUMA)
- Removes NUMA sched feature

Srikar Dronamraju (3):
  sched/numa: Rename numabalancing_enabled to sched_numa_balancing
  sched/numa: Disable sched_numa_balancing on uma systems
  sched/numa: Remove NUMA sched feature

 kernel/sched/core.c     | 16 +++-------------
 kernel/sched/fair.c     |  8 ++++----
 kernel/sched/features.h | 16 ----------------
 kernel/sched/sched.h    | 10 ++--------
 4 files changed, 9 insertions(+), 41 deletions(-)

-- 
1.8.3.1

--
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/