| Summary: | [UPDATE REQUEST] [UPSTREAM UPDATE] irqbalance | ||
|---|---|---|---|
| Product: | Server Bugs | Reporter: | Andrew Lukoshko <andrew.lukoshko> |
| Component: | Main Packages | Assignee: | Andrew Lukoshko <andrew.lukoshko> |
| Status: | RESOLVED FIXED | QA Contact: | ROSA Server Bugs <server-bugs> |
| Severity: | normal | ||
| Priority: | Normal | CC: | v.potapov |
| Version: | unspecified | Flags: | v.potapov:
qa_verified+
andrew.lukoshko: published_server+ |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | ISO-related: | ||
| Bad POT generating: | Upstream: | ||
|
Description
Andrew Lukoshko
2014-02-25 16:31:03 MSK
irqbalance-1.0.4-8.res6 http://abf-downloads.rosalinux.ru/rosa-server65/container/1658374/ http://abf-downloads.rosalinux.ru/rosa-server65/container/1658375/ *************************** RHEL Advisory *************************** * Previously, the irqbalance daemon did not consider the NUMA node assignment for an IRQ (interrupt request) for the banned CPU set. Consequently, irqbalance set the affinity incorrectly when the IRQBALANCE_BANNED_IRQS variable was set to a single CPU. In addition, IRQs could not be assigned to a node that had no eligible CPUs. Node assignment has been restricted to nodes that have eligible CPUs as defined by the unbanned_cpus bitmask, thus fixing the bug. As a result, irqbalance now sets affinity properly, and IRQs are assigned to the respective nodes correctly. * Prior to this update, the dependency of the irqbalance daemon was set incorrectly referring to a wrong kernel version. As a consequence, irqbalance could not balance IRQs on NUMA systems. With this update, the dependency has been fixed, and IRQs are now balanced correctly on NUMA systems. ************************************************************************ QA Verified |