Bug 1036065 - IRQBALANCE_BANNED_CPUS doesn't work
Summary: IRQBALANCE_BANNED_CPUS doesn't work
Keywords:
Status: CLOSED DUPLICATE of bug 1039178
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: irqbalance
Version: 6.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Petr Holasek
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-29 10:32 UTC by James Hogarth
Modified: 2018-12-05 16:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-23 13:40:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description James Hogarth 2013-11-29 10:32:52 UTC 
Description of problem:
The issue is that in activate.c, applied_mask variable gets set to the cpu mask of the "local_cpus" value of the device. This ignores anything in banned_cpus.

So, made the change in the attached patch, which basically just does a cpus_andnot and makes sure that the resulting mask isn't 0.

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

How reproducible:
Always

Steps to Reproduce:
1. Follow steps upstream


Actual results:
Specific CPU's won't be banned in a NUMA setup

Expected results:
Specific CPU's be banned in a NUMA setup

Additional info:
https://code.google.com/p/irqbalance/issues/detail?id=43
Fixed upstream in 1.0.6 git commit 1d8948271e2e81a7155ebe6c1b0abbead75416a
Note You need to log in before you can comment on or make changes to this bug.