[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <570681DD.5020208@boundarydevices.com>
Date: Thu, 7 Apr 2016 08:50:53 -0700
From: Troy Kisky <troy.kisky@...ndarydevices.com>
To: David Miller <davem@...emloft.net>
Cc: netdev@...r.kernel.org, fugang.duan@....com, lznuaa@...il.com,
fabio.estevam@....com, l.stach@...gutronix.de, andrew@...n.ch,
tremyfr@...il.com, gerg@...inux.org,
linux-arm-kernel@...ts.infradead.org, johannes@...solutions.net,
stillcompiling@...il.com, sergei.shtylyov@...entembedded.com,
arnd@...db.de
Subject: Re: [PATCH net-next V3 05/16] net: fec: reduce interrupts
On 4/6/2016 8:57 PM, David Miller wrote:
> From: Troy Kisky <troy.kisky@...ndarydevices.com>
> Date: Wed, 6 Apr 2016 17:42:47 -0700
>
>> Sure, that's an easy change. But if a TX int is what caused the
>> interrupt and masks them, and then a RX packet happens before napi
>> runs, do you want the TX serviced 1st, or RX ?
>
> If you properly split your driver up into seperate interrupt/poll
> instances, one for TX one for RX, you wouldn't need to ask me
> that question now would you?
>
> :-)
>
I absolutely claim no ownership :-)
Powered by blists - more mailing lists