The tuneable interrupt rate code is not mine, and looking at it I'm not
entirely
sure it works. Why are you focused on the interrupt rate anyway, do you have
some reason to tie it to the watchdog?
You could turn AIM off (enable_aim) and see if that changed anything?
It seems most the time problems show up they involve the use of lagg, if you
take it out of the mix does the problem go away?
Jack
On Fri, Jan 9, 2015 at 2:03 AM, Harald Schmalzbauer <
h.schmalzbauer at omnilan.de> wrote:
> Bez?glich Harald Schmalzbauer's Nachricht vom 08.01.2015 11:22
> (localtime):
>
> ...
>
> > While systat tells:
> > 3 igb1:que 0
> > 1619 igb1:que 1
> > 3 igb1:que 2
> > 1 igb1:que 3
> >
> > sysctl dev.igb tells:
> > dev.igb.1.queue0.interrupt_rate: 43478
> > dev.igb.1.queue1.interrupt_rate: 76923
> > dev.igb.1.queue2.interrupt_rate: 111111
> > dev.igb.1.queue3.interrupt_rate: 90909
> >
> > How do I have to understand sysctl's interrupt_rate value?
>
> Even more interesting, is it reasonable to get constantly visually
> strange results from igb0's interrupt_rate?
> 'sysctl dev.igb | grep rate'
> dev.igb.0.queue0.interrupt_rate: 111111
> dev.igb.0.queue1.interrupt_rate: 111111
> dev.igb.0.queue2.interrupt_rate: 111111
> dev.igb.0.queue3.interrupt_rate: 41666
> dev.igb.1.queue0.interrupt_rate: 100000
> dev.igb.1.queue1.interrupt_rate: 76923
> dev.igb.1.queue2.interrupt_rate: 37037
> dev.igb.1.queue3.interrupt_rate: 52631
> ...
> dev.igb.0.queue0.interrupt_rate: 125000
> dev.igb.0.queue1.interrupt_rate: 111111
> dev.igb.0.queue2.interrupt_rate: 111111
> dev.igb.0.queue3.interrupt_rate: 66666
> dev.igb.1.queue0.interrupt_rate: 40000
> dev.igb.1.queue1.interrupt_rate: 43478
> dev.igb.1.queue2.interrupt_rate: 37037
> dev.igb.1.queue3.interrupt_rate: 52631
> ...
> dev.igb.0.queue0.interrupt_rate: 100000
> dev.igb.0.queue1.interrupt_rate: 111111
> dev.igb.0.queue2.interrupt_rate: 111111
> dev.igb.0.queue3.interrupt_rate: 100000
> dev.igb.1.queue0.interrupt_rate: 34482
> dev.igb.1.queue1.interrupt_rate: 6097
> dev.igb.1.queue2.interrupt_rate: 83333
> dev.igb.1.queue3.interrupt_rate: 76923
>
> igb0 doesn't look random enough to me ;-)
>
> Any help highly appreciated!
>
> Thanks,
>
> -Harry
>
>