Hi Alexander,
thanks for the proposal.
>
> IMHO something in igb_watchdog_task causes the latency independently from
> actual link. At first glance I would suspect igb_update_stats (called with spinlock
> held) as it seems to do a lot of reads. Maybe this stalls somehow.
> Does the latency still occur if you comment that spinlock and call to
> igb_update_stats out?
I tried that, however the result is the very same. I have the very same latency spikes as before.
I went even further. Within the function igb_watchdog_task I removed everything but the call to igb_has_link()
and the final timer reset.
However even that led to the same result.
And there I am again at the findings in one of my previous postings within this thread.
The call to igb_has_link might be a reason for the latency jitters, however I cannot really break it down into a
single piece of code that is relevant here.
Best regards
Mathias
��.n��������+%������w��{.n�����{�����ǫ���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
