From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eric Dumazet <edumazet@google.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net-next 3/4] net: dev: Makes sure netif_rx() can be invoked in any context.
Date: Thu, 3 Feb 2022 13:20:17 +0100 [thread overview]
Message-ID: <YfvIgdEmIh6cgk3f@linutronix.de> (raw)
In-Reply-To: <20220202085004.6bab2fe5@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 2022-02-02 08:50:04 [-0800], Jakub Kicinski wrote:
> On Wed, 2 Feb 2022 13:28:47 +0100 Sebastian Andrzej Siewior wrote:
> > so they can be removed once they are no more users left.
>
> Any plans for doing the cleanup?
Sure. If this is not rejected I can go and hunt netif_rx_ni() and
netif_rx_any_context().
Sebastian
next prev parent reply other threads:[~2022-02-03 12:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 12:28 [PATCH net-next 0/4] net: dev: PREEMPT_RT fixups Sebastian Andrzej Siewior
2022-02-02 12:28 ` [PATCH net-next 1/4] net: dev: Remove the preempt_disable() in netif_rx_internal() Sebastian Andrzej Siewior
2022-02-02 17:10 ` Eric Dumazet
2022-02-03 12:00 ` Toke Høiland-Jørgensen
2022-02-03 12:17 ` Sebastian Andrzej Siewior
2022-02-03 12:41 ` Toke Høiland-Jørgensen
2022-02-03 15:50 ` Sebastian Andrzej Siewior
2022-02-04 15:20 ` [PATCH net-next v2 1/4] net: dev: Remove preempt_disable() and get_cpu() " Sebastian Andrzej Siewior
2022-02-04 16:31 ` Jakub Kicinski
2022-02-04 16:42 ` Sebastian Andrzej Siewior
2022-02-04 16:32 ` Eric Dumazet
2022-02-03 12:16 ` [PATCH net-next 1/4] net: dev: Remove the preempt_disable() " Sebastian Andrzej Siewior
2022-02-02 12:28 ` [PATCH net-next 2/4] net: dev: Remove get_cpu() " Sebastian Andrzej Siewior
2022-02-02 17:14 ` Eric Dumazet
2022-02-03 12:14 ` Toke Høiland-Jørgensen
2022-02-02 12:28 ` [PATCH net-next 3/4] net: dev: Makes sure netif_rx() can be invoked in any context Sebastian Andrzej Siewior
2022-02-02 16:50 ` Jakub Kicinski
2022-02-03 12:20 ` Sebastian Andrzej Siewior [this message]
2022-02-03 19:38 ` Jakub Kicinski
2022-02-02 17:43 ` Eric Dumazet
2022-02-03 12:19 ` Toke Høiland-Jørgensen
2022-02-03 15:10 ` Sebastian Andrzej Siewior
2022-02-03 15:25 ` Eric Dumazet
2022-02-03 15:40 ` Sebastian Andrzej Siewior
2022-02-03 16:18 ` Eric Dumazet
2022-02-03 16:44 ` Sebastian Andrzej Siewior
2022-02-03 17:45 ` Sebastian Andrzej Siewior
2022-02-04 13:00 ` [PATCH net-next v2 " Sebastian Andrzej Siewior
2022-02-04 18:46 ` Eric Dumazet
2022-02-02 12:28 ` [PATCH net-next 4/4] net: dev: Make rps_lock() disable interrupts Sebastian Andrzej Siewior
2022-02-02 16:47 ` Jakub Kicinski
2022-02-03 16:41 ` [PATCH net-next v2 " Sebastian Andrzej Siewior
2022-02-03 19:39 ` Jakub Kicinski
2022-02-02 16:14 ` [PATCH net-next 0/4] net: dev: PREEMPT_RT fixups Jakub Kicinski
2022-02-03 11:59 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfvIgdEmIh6cgk3f@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.