Bug 712252

Summary:	vmscan: correctly check if reclaimer should schedule during shrink_slab
Product:	Red Hat Enterprise Linux 6	Reporter:	Andrea Arcangeli <aarcange>
Component:	kernel	Assignee:	Andrea Arcangeli <aarcange>
Status:	CLOSED ERRATA	QA Contact:	Caspar Zhang <czhang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	czhang, juzhang, kzhang, qcai, tburke
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel-2.6.32-169.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 13:38:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Andrea Arcangeli 2011-06-09 23:25:41 UTC

Description of problem: It has been reported on some laptops that kswapd is consuming large amounts of CPU and not being scheduled when SLUB is enabled during large amounts of file copying.


Version-Release number of selected component (if applicable):


How reproducible: not clear


Steps to Reproduce:
1. run a large amount of small file copying
2.
3.
  
Actual results: higher kswapd utilization


Expected results: lower kswapd untilization and better latency


Additional info:

Comment 2 RHEL Program Management 2011-06-13 09:29:54 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 3 Aristeu Rozanski 2011-07-18 15:27:54 UTC

Patch(es) available on kernel-2.6.32-169.el6

Comment 7 errata-xmlrpc 2011-12-06 13:38:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1530.html