Bug 683513

Summary:	NUMA aware scheduling & memory allocation
Product:	Red Hat Enterprise Linux 7	Reporter:	Rik van Riel <riel>
Component:	kernel	Assignee:	Rik van Riel <riel>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0	CC:	aarcange, aquini, djuran, hannsj_uhl, hhuang, juzhang, knoel, lsmid, lwoodman, michen, nobody+295318, perfbz, pholasek, qcai, sdenham, svenkatr, tsmetana, ypu
Target Milestone:	alpha	Keywords:	FutureFeature
Target Release:	7.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel-3.10.0-35.el7	Doc Type:	Release Note
Doc Text:	NUMA-Aware Scheduling and Memory Allocation In Red Hat Enterprise Linux 7.0, the kernel automatically relocates processes and memory between NUMA nodes in the same system, in order to improve performance on systems with non-uniform memory access (NUMA).	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 11:27:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	817917, 824630, 824634, 824636, 824980, 872549, 919431, 985488, 1032535, 1032538, 1071730

Description Rik van Riel 2011-03-09 15:54:22 UTC

Description of problem:

Give processes a NUMA home node, try to schedule them near their memory and implement a low impact way of load balancing the processes between NUMA nodes.

Needs to be accepted upstream and solve the problem for many people and many workloads.

Comment 4 Jarod Wilson 2013-10-18 12:48:36 UTC

Patch(es) available on kernel-3.10.0-35.el7

Comment 6 Linda Wang 2013-10-21 21:12:46 UTC

*** Bug 909252 has been marked as a duplicate of this bug. ***

Comment 9 Hai Huang 2013-12-18 19:30:32 UTC

*** Bug 817919 has been marked as a duplicate of this bug. ***

Comment 10 Ludek Smid 2014-06-13 11:27:55 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.