Bug 163381

Summary: RHEL3U5 x86-64 : xw9300 & numa=on swaps behaviour is unexpected
Product: Red Hat Enterprise Linux 3 Reporter: Issue Tracker <tao>
Component: kernelAssignee: Larry Woodman <lwoodman>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jparadis, petrides, tao, tburke
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0144 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-15 16:16:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 168424    

Description Issue Tracker 2005-07-15 18:40:15 UTC
Escalated to Bugzilla from IssueTracker

Comment 30 Jim Paradis 2005-08-16 19:07:52 UTC
I'll try the reproducer, but my opinion at this point is that this is a known
issue with RHEL3 NUMA that will not be fixed in an update.  Basically, NUMA will
allocate all memory on a thread's home node before resorting to using other
nodes.  This causes swapping to occur when we get over the swap threshold for a
given node, even if other nodes have plenty of free memory.  Fixing this would
require either swap parameter changes or significant invasive VM changes that
are too invasive for a late update, in my opinion.


Comment 35 Ernie Petrides 2005-08-29 21:19:09 UTC
This is essentially a duplicate of bug 130387.

Comment 37 Ernie Petrides 2005-11-30 07:49:11 UTC
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-37.12.EL).

To enable an improved NUMA-friendly page allocation policy, please
set /proc/sys/vm/numa_memory_allocator via the "sysctl" command
(or put "vm.numa_memory_allocator = 1" in /etc/sysctl.conf).


Comment 39 Peter Martuccelli 2005-12-08 14:52:16 UTC
Bug fix, Devel ACK.

Comment 42 Red Hat Bugzilla 2006-03-15 16:16:14 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0144.html