Your message dated Mon, 06 May 2019 13:10:11 +
with message-id
and subject line Bug#926967: fixed in linux 4.19.37-1
has caused the Debian Bug report #926967,
regarding Don't recommend irqbalance (was: Re: Handling irqbalance in virtual
environments)
to be marked as done.
This means
Control: severity -1 serious
On Fri, Apr 12, 2019 at 10:56:29PM +0200, Bastian Blank wrote:
> > Then let's drop the recommendation.
> Okay.
After re-evaluating, I'll consider that a blocker.
Regards,
Bastian
--
The more complex the mind, the greater the need for the simplicity of play.
Processing control commands:
> severity -1 serious
Bug #926967 [src:linux] Don't recommend irqbalance (was: Re: Handling
irqbalance in virtual environments)
Severity set to 'serious' from 'important'
--
926967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92696
On Fri, Apr 12, 2019 at 10:56:29PM +0200, Bastian Blank wrote:
> > On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote:
> > > It turns out we got again problems with irqbalance.
> > >
> > > It was added as recommends of the main image in 3.16, as it was reported
> > > that older kernels move al
Package: src:linux
Version: 4.19.28-2
Severity: important
On Fri, Apr 12, 2019 at 09:10:32PM +0100, Ben Hutchings wrote:
> On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote:
> > It turns out we got again problems with irqbalance.
> >
> > It was added as recommends of the main image in 3.16,
On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote:
> Moin
>
> It turns out we got again problems with irqbalance.
>
> It was added as recommends of the main image in 3.16, as it was reported
> that older kernels move all interrupts to CPU 0 without help.[1]
>
> In the meantime the kernel ca
On Fri, Apr 12, 2019 at 10:53:47AM +0200, Bastian Blank wrote:
> With 4.19, even on real hardware, where interrupts have an affinity for
> all cpus, each interrupt is actually delivered to different cpu.
It seems a lot of this comes from
https://lore.kernel.org/patchwork/cover/801590/
Regards,
Ba
Moin
It turns out we got again problems with irqbalance.
It was added as recommends of the main image in 3.16, as it was reported
that older kernels move all interrupts to CPU 0 without help.[1]
In the meantime the kernel can do balancing on it's own. In 4.9, I've
seen it working with aacraid,
8 matches
Mail list logo
