RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 844381 - --hint-policy=subset not respected if balance level is higher than CORE
Summary: --hint-policy=subset not respected if balance level is higher than CORE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: irqbalance
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Holasek
QA Contact: Evan McNabb
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 12:55 UTC by Paolo Bonzini
Modified: 2019-02-15 03:09 UTC (History)
4 users (show)

Fixed In Version: irqbalance-1.0.3-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:12:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Paolo Bonzini 2012-07-30 12:55:15 UTC 
Description of problem:
See http://code.google.com/p/irqbalance/issues/detail?id=37.  This causes irqbalance to fail setting up affinity correctly for multiqueue virtio-scsi devices.

Version-Release number of selected component (if applicable):
1.0.3-7.fc18

How reproducible:
100%

Steps to Reproduce:
1. Start a virtual machine with QEMU >= 1.2 (will be in Beta 1) and -smp 4 -device virtio-scsi-pci,num_queues=4.
2. Stop irqbalance.
3. Look in /proc/interrupts for the four virtio-request interrupts, assign the affinity hints (/proc/irq/NUM/affinity_hint) respectively to 1 2 4 8.
4. Start irqbalance --oneshot --hint-policy=exact.
5. Look at the affinity that is set in /proc/irq/NUM/smp_affinity. 
 
Actual results:
No affinity, smp_affinity is "f" for all four interrupts

Expected results:
smp_affinity matches affinity hint.

Additional info:
The same results occur also with --hint-policy=subset (the default).

This is because PCI storage adapters are BALANCE_CACHE and, on a system with one NUMA node and one cache domain, irqbalance finds nothing to do.  The attached patch does two things: 1) it forces the first execution of activate_mappings to consider all interrupts; 2) it forces activate_mapping to do something even for interrupts without assigned objects, if the hint policy is not ignore.

Future kernel patches will make steps 2-3-4 redundant.
Comment 1 Paolo Bonzini 2012-08-07 16:31:07 UTC 
Further analysis pointed to two bugs:

- one is general brokenness of irqbalance on non-NUMA machines, and affects both exact and subset hint policies (fixed by commit 1189cd6f)

- the other is specific to affinity hints with --hintpolicy=subset (fixed in commit 638d405beed670b96258171bfe8363fae1569167)
Comment 3 Ludek Smid 2014-06-13 11:12:35 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.
Note You need to log in before you can comment on or make changes to this bug.