[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Package conflicts, breaks, and problematic upgrades... with irqbalance

On Tue, Feb 27, 2018 at 12:33 PM Bastian Blank <waldi@debian.org> wrote:
On Tue, Feb 27, 2018 at 07:14:38PM +0000, Zach Marano wrote:
> irqbalance is supposed to spread interrupts across all CPU's but in GCE
> (and from what I recall KVM as well) it ends up assigning all interrupts to
> CPU0. It may be considered broken except that it was originally meant for
> bare metal hardware and therefore- maybe its not actually broken in a
> virtual environment?

Sure it is broken if it does no sensible things.  If it can't do
anything, it should be a no-op and do nothing.

> With irqbalance on a 32 core VM:
> for i in $(seq 0 300); do grep . /proc/irq/$i/smp_affinity /dev/null
> 2>/dev/null; done
> /proc/irq/0/smp_affinity:ffffffff
> /proc/irq/1/smp_affinity:ffffffff
> /proc/irq/2/smp_affinity:ffffffff
> /proc/irq/3/smp_affinity:ffffffff

This looks for me like it just does not manage to balance anything.

However, I just started a system on GCE with 64 cores, installed
irqbalance and are greeted with this:


So it does something.

Yes, that is our script doing that. Reboot and see what irqbalance does.

Each kiss is as the first.
                -- Miramanee, Kirk's wife, "The Paradise Syndrome",
                   stardate 4842.6

Reply to: