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 591515 - need to backport affinity_hint for irqbalance
Summary: need to backport affinity_hint for irqbalance
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: irqbalance
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anton Arapov
QA Contact: Evan McNabb
URL:
Whiteboard:
Depends On: 591509
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 13:37 UTC by Neil Horman
Modified: 2014-06-18 08:02 UTC (History)
2 users (show)

Fixed In Version: irqbalance-0.55-26
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 13:59:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
backport of the needed patch (4.46 KB, patch)
2010-06-09 20:27 UTC, Neil Horman 		no flags Details | Diff
View All

Description Neil Horman 2010-05-12 13:37:56 UTC 
Description of problem:

http://code.google.com/p/irqbalance/source/detail?r=25
Comment 2 RHEL Program Management 2010-05-12 15:46:21 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Neil Horman 2010-06-09 20:27:32 UTC 
Created attachment 422693 [details]
backport of the needed patch

backport of the needed patch.  I still need to test this out
Comment 4 Neil Horman 2010-06-09 20:30:53 UTC 
testing on amd-toonie2-02
Comment 5 Neil Horman 2010-06-10 15:37:59 UTC 
patch tested and working, will check in as soon as this is approved.
Comment 6 RHEL Program Management 2010-07-15 14:27:01 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 9 Neil Horman 2010-08-23 17:54:47 UTC 
Its not a per-system thing.  Its driver specific.  Currently the ixgbe driver supports doing it, but I don't think that particular feature was backported yet, so you might need to wait for 6.1 to verify
Comment 11 releng-rhel@redhat.com 2010-11-15 13:59:44 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.