Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1361654 - irqbalance with IRQBALANCE_BANNED_CPUS and isolcpus don't act intuitive
Summary: irqbalance with IRQBALANCE_BANNED_CPUS and isolcpus don't act intuitive
Status: ON_QA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: irqbalance
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Kairui Song
QA Contact: Evan McNabb
Depends On:
Blocks: 1647768
TreeView+ depends on / blocked
Reported: 2016-07-29 16:06 UTC by Andrej Manduch
Modified: 2019-03-01 08:38 UTC (History)
4 users (show)

Fixed In Version: irqbalance-1.0.7-12.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Andrej Manduch 2016-07-29 16:06:57 UTC
Description of problem:

Few months ago in irqbalance was introduced feature which reads isolated cpu from kernel and don't assign interrupts to them.

Thing is that when you're using IRQBALANCE_BANNED_CPUS it also automatically disables this feature. Personally I think this is strange. Nevertheless I would suggest change this logic (I'm honestly not sure if logic behind this bahaviour is correct or not) or document this behaviour on man page. 

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

Comment 3 Kairui Song 2018-11-05 09:56:14 UTC
In the commit ca5a3f13 and 2dddcfef which added autodetect and ban isolated CPUs, the commit message makes it very clear that IRQBALANCE_BANNED_CPUS will override the automatically detected banned_cpus, so it's intended to do so.
I'll update the man page so this will be no longer confusing.

Note You need to log in before you can comment on or make changes to this bug.