[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yf7ftf+6j52opu5w@linutronix.de>
Date: Sat, 5 Feb 2022 21:36:05 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Jakub Kicinski <kuba@...nel.org>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Eric Dumazet <edumazet@...gle.com>,
Jesper Dangaard Brouer <hawk@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Toke Høiland-Jørgensen <toke@...e.dk>
Subject: Re: [PATCH net-next v2 2/3] net: dev: Makes sure netif_rx() can be
invoked in any context.
On 2022-02-04 20:17:15 [-0800], Jakub Kicinski wrote:
> On Fri, 4 Feb 2022 21:12:58 +0100 Sebastian Andrzej Siewior wrote:
> > +int __netif_rx(struct sk_buff *skb)
> > +{
> > + int ret;
> > +
> > + trace_netif_rx_entry(skb);
> > + ret = netif_rx_internal(skb);
> > + trace_netif_rx_exit(ret);
> > + return ret;
> > +}
>
> Any reason this is not exported? I don't think there's anything wrong
> with drivers calling this function, especially SW drivers which already
> know to be in BH. I'd vote for roughly all of $(ls drivers/net/*.c) to
> get the same treatment as loopback.
Don't we end up in the same situation as netif_rx() vs netix_rx_ni()?
Sebastian
Powered by blists - more mailing lists