irqban questions

[Joe Lawrence]

Duh.. of course.  Thanks again!

-- Joe

On 06/24/2016 05:06 PM, Neil Horman wrote:
> Sure, it can, just add:
> Echo (mask) >/proc/irq/n/smp-affinity
> To the policy script
> Neil
> 
> 
> On Fri, Jun 24, 2016, 16:59 Joe Lawrence <joe.lawrence at stratus.com
> <mailto:joe.lawrence at stratus.com>> wrote:
> 
>     Thanks Neil, policyscript looks promising.  From the manpage, irqbalance
>     will understand "ban, balance_level, and numa_node", so I don't suppose
>     the policyscript can provide the smp_affinity directly?
> 
>     -- Joe
> 
>     On 06/24/2016 04:43 PM, Neil Horman wrote:
>     > Hey Joe,
>     >
>     >      You have a few choices.  You can do exactly what you are
>     describing
>     > above, or you can use the policy-script option.
>     >
>     > The option you provide, one in which you compute the irqs you want to
>     > ignore (or ban, in the irqbalance man page parlance) in the sysconfig
>     > file is not really used that often, but might be handy in some cases.
>     >
>     > The more common method is using the policyscrpt option, in which you
>     > provide irqbalance with the name of a script to run for each
>     discovered
>     > irq.  The script accepts the device sysfs path and irq number as
>     > arguments, and you can echo "ban=1" from it to tell irqbalance to
>     > ban/ignore the corresponding irq.  It should be documented in the
>     man page
>     >
>     > Neil
>     >
>     >
>     > On Fri, Jun 24, 2016 at 4:35 PM Joe Lawrence
>     <joe.lawrence at stratus.com <mailto:joe.lawrence at stratus.com>
>     > <mailto:joe.lawrence at stratus.com
>     <mailto:joe.lawrence at stratus.com>>> wrote:
>     >
>     >     Hi Neil et al,
>     >
>     >     I was wondering about the best way to configure irqbalance to
>     ignore
>     >     particular IRQs without hard-coding their IRQ numbers into
>     >     /etc/sysconfig/irqbalance or manually starting the daemon.
>     >
>     >     I was wondering if something like this would work:
>     >
>     >        IRQBALANCE_ARGS="--banirq=$(get IRQ1#) --banirq=$(get IRQ2#)"
>     >
>     >     or better yet:
>     >
>     >       IRQBALANCE_ARGS="--banirq=desc1 --banirq=desc2"
>     >
>     >     where descX would be the IRQ description.
>     >
>     >
>     >     Alternatively, is there anyway to mark irqs as banned once the
>     daemon
>     >     has already started?
>     >
>     >
>     >     Thanks,
>     >
>     >     -- Joe
>     >
>