[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <225290e4-02be-483b-855f-5215424286b0@gmail.com>
Date: Tue, 16 Oct 2018 17:21:45 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>,
Holger Hoffstätte <holger@...lied-asynchrony.com>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
David Miller <davem@...emloft.net>,
Realtek linux nic maintainers <nic_swsd@...ltek.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net] r8169: fix NAPI handling under high load
On 10/16/2018 04:03 PM, Stephen Hemminger wrote:
> Many drivers have buggy usage of napi_complete_done.
>
> Might even be worth forcing all network drivers to check the return
> value. But fixing 150 broken drivers will be a nuisance.
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index dc1d9ed33b31..c38bc66ffe74 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -466,7 +466,8 @@ static inline bool napi_reschedule(struct napi_struct *napi)
> return false;
> }
>
> -bool napi_complete_done(struct napi_struct *n, int work_done);
> +bool __must_check napi_complete_done(struct napi_struct *n, int work_done);
> +
> /**
> * napi_complete - NAPI processing complete
> * @n: NAPI context
>
I disagree completely.
This never has been a requirement.
Powered by blists - more mailing lists