From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Hou Tao <houtao@huaweicloud.com>, bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Björn Töpel" <bjorn.topel@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Song Liu" <song@kernel.org>, "Hao Luo" <haoluo@google.com>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"KP Singh" <kpsingh@kernel.org>,
"Stanislav Fomichev" <sdf@google.com>,
"Jiri Olsa" <jolsa@kernel.org>,
houtao1@huawei.com
Subject: Re: [RFC PATCH bpf-next 2/2] bpf, cpumap: Clean up bpf_cpu_map_entry directly in cpu_map_free
Date: Thu, 10 Aug 2023 12:22:10 +0200 [thread overview]
Message-ID: <87fs4rfb8t.fsf@toke.dk> (raw)
In-Reply-To: <20230728023030.1906124-3-houtao@huaweicloud.com>
Hou Tao <houtao@huaweicloud.com> writes:
> From: Hou Tao <houtao1@huawei.com>
>
> After synchronize_rcu(), both the dettached XDP program and
> xdp_do_flush() are completed, and the only user of bpf_cpu_map_entry
> will be cpu_map_kthread_run(), so instead of calling
> __cpu_map_entry_replace() to empty queue and do cleanup after a RCU
> grace period, do these things directly.
>
> Signed-off-by: Hou Tao <houtao1@huawei.com>
With one nit below:
Reviewed-by: Toke Høiland-Jørgensen <toke@redhat.com>
> ---
> kernel/bpf/cpumap.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/bpf/cpumap.c b/kernel/bpf/cpumap.c
> index 24f39c37526f..f8e2b24320c0 100644
> --- a/kernel/bpf/cpumap.c
> +++ b/kernel/bpf/cpumap.c
> @@ -554,16 +554,15 @@ static void cpu_map_free(struct bpf_map *map)
> /* At this point bpf_prog->aux->refcnt == 0 and this map->refcnt == 0,
> * so the bpf programs (can be more than one that used this map) were
> * disconnected from events. Wait for outstanding critical sections in
> - * these programs to complete. The rcu critical section only guarantees
> - * no further "XDP/bpf-side" reads against bpf_cpu_map->cpu_map.
> - * It does __not__ ensure pending flush operations (if any) are
> - * complete.
> + * these programs to complete. synchronize_rcu() below not only
> + * guarantees no further "XDP/bpf-side" reads against
> + * bpf_cpu_map->cpu_map, but also ensure pending flush operations
> + * (if any) are complete.
> */
> -
> synchronize_rcu();
>
> - /* For cpu_map the remote CPUs can still be using the entries
> - * (struct bpf_cpu_map_entry).
> + /* The only possible user of bpf_cpu_map_entry is
> + * cpu_map_kthread_run().
> */
> for (i = 0; i < cmap->map.max_entries; i++) {
> struct bpf_cpu_map_entry *rcpu;
> @@ -572,8 +571,8 @@ static void cpu_map_free(struct bpf_map *map)
> if (!rcpu)
> continue;
>
> - /* bq flush and cleanup happens after RCU grace-period */
> - __cpu_map_entry_replace(cmap, i, NULL); /* call_rcu */
> + /* Empty queue and do cleanup directly */
The "empty queue" here is a bit ambiguous, maybe "Stop kthread and
cleanup entry"?
> + __cpu_map_entry_free(&rcpu->free_work.work);
> }
> bpf_map_area_free(cmap->cpu_map);
> bpf_map_area_free(cmap);
> --
> 2.29.2
next prev parent reply other threads:[~2023-08-10 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 2:30 [RFC PATCH bpf-next 0/2] Remove unnecessary synchronizations in cpumap Hou Tao
2023-07-28 2:30 ` [RFC PATCH bpf-next 1/2] bpf, cpumap: Use queue_rcu_work() to remove unnecessary rcu_barrier() Hou Tao
2023-08-10 10:16 ` Toke Høiland-Jørgensen
2023-08-11 10:22 ` Hou Tao
2023-07-28 2:30 ` [RFC PATCH bpf-next 2/2] bpf, cpumap: Clean up bpf_cpu_map_entry directly in cpu_map_free Hou Tao
2023-08-10 10:22 ` Toke Høiland-Jørgensen [this message]
2023-08-11 10:23 ` Hou Tao
2023-08-10 3:22 ` [RFC PATCH bpf-next 0/2] Remove unnecessary synchronizations in cpumap Hou Tao
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=87fs4rfb8t.fsf@toke.dk \
--to=toke@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.