From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Hou Tao <houtao@huaweicloud.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
bpf <bpf@vger.kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
Hao Luo <haoluo@google.com>, Yonghong Song <yhs@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Jiri Olsa <jolsa@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
rcu@vger.kernel.org, "houtao1@huawei.com" <houtao1@huawei.com>
Subject: Re: [RFC PATCH bpf-next v4 0/3] Handle immediate reuse in bpf memory allocator
Date: Wed, 7 Jun 2023 21:30:41 -0700 [thread overview]
Message-ID: <CAADnVQ+a4Ng0TEoK7W+KG1JfMvjzhdBNtSOx_2z0Mi=Fz1A0PA@mail.gmail.com> (raw)
In-Reply-To: <a12008e9-f3f7-5050-e461-344d9d86e48f@huaweicloud.com>
On Wed, Jun 7, 2023 at 8:36 PM Hou Tao <houtao@huaweicloud.com> wrote:
>
> below. And Alexei, could you please also try the hack below for your
> multiple-rcu-cbs version ?
Before any further experiments... please fix the bench in patch 2.
Make sure it exits out of RCU CS after no more than 64 map_update_elem.
Just send that patch alone.
next prev parent reply other threads:[~2023-06-08 4:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 3:53 [RFC PATCH bpf-next v4 0/3] Handle immediate reuse in bpf memory allocator Hou Tao
2023-06-06 3:53 ` [RFC PATCH bpf-next v4 1/3] bpf: Factor out a common helper free_all() Hou Tao
2023-06-06 3:53 ` [RFC PATCH bpf-next v4 2/3] selftests/bpf: Add benchmark for bpf memory allocator Hou Tao
2023-06-06 21:13 ` Alexei Starovoitov
2023-06-07 1:32 ` Hou Tao
2023-06-06 3:53 ` [RFC PATCH bpf-next v4 3/3] bpf: Only reuse after one RCU GP in " Hou Tao
2023-06-06 12:30 ` [RFC PATCH bpf-next v4 0/3] Handle immediate reuse " Hou Tao
2023-06-06 21:04 ` Alexei Starovoitov
2023-06-07 1:19 ` Hou Tao
2023-06-07 1:39 ` Alexei Starovoitov
2023-06-07 7:56 ` Hou Tao
2023-06-07 8:42 ` Hou Tao
2023-06-07 17:52 ` Alexei Starovoitov
2023-06-07 20:50 ` Alexei Starovoitov
2023-06-07 23:23 ` Alexei Starovoitov
2023-06-07 23:30 ` Paul E. McKenney
2023-06-07 23:50 ` Alexei Starovoitov
2023-06-08 0:13 ` Paul E. McKenney
2023-06-08 0:34 ` Alexei Starovoitov
2023-06-08 1:15 ` Paul E. McKenney
2023-06-08 3:35 ` Hou Tao
2023-06-08 4:30 ` Hou Tao
2023-06-08 4:30 ` Alexei Starovoitov [this message]
2023-06-08 1:57 ` Hou Tao
2023-06-08 1:51 ` Hou Tao
2023-06-08 2:55 ` Paul E. McKenney
2023-06-08 3:43 ` Hou Tao
2023-06-08 16:18 ` Paul E. McKenney
2023-06-09 3:02 ` Hou Tao
2023-06-09 14:30 ` Paul E. McKenney
2023-06-12 2:03 ` Hou Tao
2023-06-12 3:40 ` Paul E. McKenney
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='CAADnVQ+a4Ng0TEoK7W+KG1JfMvjzhdBNtSOx_2z0Mi=Fz1A0PA@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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 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).