On Wed, 3 Feb 2016, Rik van Riel wrote:
> On 02/03/2016 01:52 PM, Thomas Gleixner wrote:
> > From: Thomas Gleixner Date: Fri May 25
> > 16:59:47 2012 +0200 Subject: genirq: Add default affinity mask
> > command line option
> >
> > If we isolate CPUs, then we don't want random device interrupts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/03/2016 01:52 PM, Thomas Gleixner wrote:
> From: Thomas Gleixner Date: Fri May 25
> 16:59:47 2012 +0200 Subject: genirq: Add default affinity mask
> command line option
>
> If we isolate CPUs, then we don't want random device interrupts on
>
From: Thomas Gleixner
Date: Fri May 25 16:59:47 2012 +0200
Subject: genirq: Add default affinity mask command line option
If we isolate CPUs, then we don't want random device interrupts on them. Even
w/o the user space irq balancer enabled we can end up with irqs on non boot
cpus and chasing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/03/2016 01:52 PM, Thomas Gleixner wrote:
> From: Thomas Gleixner Date: Fri May 25
> 16:59:47 2012 +0200 Subject: genirq: Add default affinity mask
> command line option
>
> If we isolate CPUs, then we don't want random
On Wed, 3 Feb 2016, Rik van Riel wrote:
> On 02/03/2016 01:52 PM, Thomas Gleixner wrote:
> > From: Thomas Gleixner Date: Fri May 25
> > 16:59:47 2012 +0200 Subject: genirq: Add default affinity mask
> > command line option
> >
> > If we isolate CPUs, then we don't want random
From: Thomas Gleixner
Date: Fri May 25 16:59:47 2012 +0200
Subject: genirq: Add default affinity mask command line option
If we isolate CPUs, then we don't want random device interrupts on them. Even
w/o the user space irq balancer enabled we can end up with irqs on non boot
6 matches
Mail list logo