From: "Björn Töpel" <bjorn.topel@intel.com> To: "Toke Høiland-Jørgensen" <toke@redhat.com>, "Björn Töpel" <bjorn.topel@gmail.com>, ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org, bpf@vger.kernel.org Cc: magnus.karlsson@intel.com, maciej.fijalkowski@intel.com, kuba@kernel.org, jonathan.lemon@gmail.com, maximmi@nvidia.com, davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com, ciara.loftus@intel.com, weqaar.a.janjua@intel.com Subject: Re: [PATCH bpf-next v2 1/8] xdp: restructure redirect actions Date: Wed, 20 Jan 2021 18:26:23 +0100 [thread overview] Message-ID: <559c6eb8-38b3-4719-2368-397f07daf5a5@intel.com> (raw) In-Reply-To: <87bldj4lm6.fsf@toke.dk> On 2021-01-20 17:30, Toke Høiland-Jørgensen wrote: > Björn Töpel <bjorn.topel@intel.com> writes: > [...] >> >> It can't be free'd but, ri->map can be cleared via >> bpf_clear_redirect_map(). So, between the helper (setting) and the >> tracepoint in xdp_do_redirect() it can be cleared (say if the XDP >> program is swapped out, prior running xdp_do_redirect()). > > But xdp_do_redirect() should be called on driver flush before exiting > the NAPI cycle, so how can the XDP program be swapped out? > To clarify; xdp_do_redirect() is called for each packet in the NAPI poll loop. Yeah, you're right. The xdp_do_redirect() is within the RCU scope, so the program wont be destroyed (but can be swapped though!). Hmm, so IOW the bpf_clear_redirect_map() is not needed anymore... Björn [...]
next prev parent reply other threads:[~2021-01-20 17:36 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-19 15:50 [PATCH bpf-next v2 0/8] Introduce bpf_redirect_xsk() helper Björn Töpel 2021-01-19 15:50 ` [PATCH bpf-next v2 1/8] xdp: restructure redirect actions Björn Töpel 2021-01-20 12:44 ` Toke Høiland-Jørgensen 2021-01-20 13:40 ` Björn Töpel 2021-01-20 14:52 ` Toke Høiland-Jørgensen 2021-01-20 15:49 ` Björn Töpel 2021-01-20 16:30 ` Toke Høiland-Jørgensen 2021-01-20 17:26 ` Björn Töpel [this message] 2021-01-19 15:50 ` [PATCH bpf-next v2 2/8] xsk: remove explicit_free parameter from __xsk_rcv() Björn Töpel 2021-01-19 15:50 ` [PATCH bpf-next v2 3/8] xsk: fold xp_assign_dev and __xp_assign_dev Björn Töpel 2021-01-19 15:50 ` [PATCH bpf-next v2 4/8] xsk: register XDP sockets at bind(), and add new AF_XDP BPF helper Björn Töpel 2021-01-20 8:25 ` kernel test robot 2021-01-20 8:41 ` Björn Töpel 2021-01-20 8:50 ` kernel test robot 2021-01-20 12:50 ` Toke Høiland-Jørgensen 2021-01-20 13:25 ` Björn Töpel 2021-01-20 14:54 ` Toke Høiland-Jørgensen 2021-01-20 15:18 ` Björn Töpel 2021-01-20 17:29 ` Toke Høiland-Jørgensen 2021-01-20 18:22 ` Björn Töpel 2021-01-20 20:26 ` Toke Høiland-Jørgensen 2021-01-20 21:15 ` Alexei Starovoitov 2021-01-21 8:18 ` Björn Töpel 2021-01-19 15:50 ` [PATCH bpf-next v2 5/8] libbpf, xsk: select AF_XDP BPF program based on kernel version Björn Töpel 2021-01-20 12:52 ` Toke Høiland-Jørgensen 2021-01-20 13:25 ` Björn Töpel 2021-01-20 14:49 ` Björn Töpel 2021-01-20 15:11 ` Toke Høiland-Jørgensen 2021-01-20 15:27 ` Björn Töpel 2021-01-20 17:30 ` Toke Høiland-Jørgensen 2021-01-20 18:25 ` Alexei Starovoitov 2021-01-20 18:30 ` Björn Töpel 2021-01-20 14:56 ` Toke Høiland-Jørgensen 2021-01-19 15:50 ` [PATCH bpf-next v2 6/8] libbpf, xsk: select bpf_redirect_xsk(), if supported Björn Töpel 2021-01-19 15:50 ` [PATCH bpf-next v2 7/8] selftest/bpf: add XDP socket tests for bpf_redirect_{xsk, map}() Björn Töpel 2021-01-21 7:39 ` Andrii Nakryiko 2021-01-21 12:31 ` Björn Töpel 2021-01-19 15:50 ` [PATCH bpf-next v2 8/8] selftest/bpf: remove a lot of ifobject casting in xdpxceiver Björn Töpel 2021-01-20 13:15 ` [PATCH bpf-next v2 0/8] Introduce bpf_redirect_xsk() helper Maxim Mikityanskiy 2021-01-20 13:27 ` Björn Töpel 2021-01-20 15:57 ` Jesper Dangaard Brouer 2021-01-20 16:19 ` Maciej Fijalkowski 2021-01-21 17:01 ` Jesper Dangaard Brouer 2021-01-22 8:59 ` Magnus Karlsson 2021-01-22 9:45 ` Maciej Fijalkowski
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=559c6eb8-38b3-4719-2368-397f07daf5a5@intel.com \ --to=bjorn.topel@intel.com \ --cc=ast@kernel.org \ --cc=bjorn.topel@gmail.com \ --cc=bpf@vger.kernel.org \ --cc=ciara.loftus@intel.com \ --cc=daniel@iogearbox.net \ --cc=davem@davemloft.net \ --cc=hawk@kernel.org \ --cc=john.fastabend@gmail.com \ --cc=jonathan.lemon@gmail.com \ --cc=kuba@kernel.org \ --cc=maciej.fijalkowski@intel.com \ --cc=magnus.karlsson@intel.com \ --cc=maximmi@nvidia.com \ --cc=netdev@vger.kernel.org \ --cc=toke@redhat.com \ --cc=weqaar.a.janjua@intel.com \ --subject='Re: [PATCH bpf-next v2 1/8] xdp: restructure redirect actions' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).