[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP8WD_aos5u90cxS5+fCL9pVziHXV==1b+j2tzwxA5qxe7Ao-w@mail.gmail.com>
Date: Mon, 10 Apr 2017 10:22:05 -0400
From: tedheadster <tedheadster@...il.com>
To: Francois Romieu <romieu@...zoreil.com>
Cc: ville.syrjala@...ux.intel.com, David Miller <davem@...emloft.net>,
eric.dumazet@...il.com, edumazet@...gle.com,
netdev <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [regression v4.11] 617f01211baf ("8139too: use napi_complete_done()")
On Sat, Apr 8, 2017 at 6:23 AM, Francois Romieu <romieu@...zoreil.com> wrote:
> David Miller <davem@...emloft.net> :
> [...]
>> One theory is that the interrupt masking isn't working properly
>> and interrupts are still arriving and hitting the NAPI state even
>> when we are actively polling NAPI.
>>
>> And this problem was masked by the locking done here.
>
> Yes.
>
> Ville, can you rule out irq sharing between the 8139 and some other
> device ? It's a candidate for unexpected interrupt handler invocation
> with older pc, even with properly working hardware.
>
Eric,
If napi_complete_done() calls could affect drivers on older
hardware, I can test the following:
drivers/net/ethernet/3com/typhoon.c
drivers/net/ethernet/amd/pcnet32.c
drivers/net/ethernet/broadcom/tg3.c
drivers/net/ethernet/dec/tulip/interrupt.c
drivers/net/ethernet/intel/e100.c
drivers/net/ethernet/intel/e1000/e1000_main.c
drivers/net/ethernet/smsc/epic100.c
drivers/net/ethernet/via/via-rhine.c
- Matthew
Powered by blists - more mailing lists