[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8447eee-31d0-f730-bc31-7e55c76135f4@iogearbox.net>
Date: Fri, 13 May 2022 17:01:30 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Feng zhou <zhoufeng.zf@...edance.com>, ast@...nel.org,
andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, rostedt@...dmis.org,
mingo@...hat.com, jolsa@...nel.org, davemarchevsky@...com,
joannekoong@...com, geliang.tang@...e.com
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, duanxiongchun@...edance.com,
songmuchun@...edance.com, wangdongdong.6@...edance.com,
cong.wang@...edance.com, zhouchengming@...edance.com,
yosryahmed@...gle.com
Subject: Re: [PATCH bpf-next v3 0/2] Introduce access remote cpu elem support
in BPF percpu map
On 5/13/22 8:39 AM, Feng zhou wrote:
[...]
> Changelog:
> ----------
> v2->v3: Addressed comments from Andrii Nakryiko.
> - use /* */ instead of //
> - use libbpf_num_possible_cpus() instead of sysconf(_SC_NPROCESSORS_ONLN)
> - use 8 bytes for value size
> - fix memory leak
> - use ASSERT_EQ instead of ASSERT_OK
> - add bpf_loop to fetch values on each possible CPU
> some details in here:
> https://lore.kernel.org/lkml/20220511093854.411-1-zhoufeng.zf@bytedance.com/T/
The v2 of your series is already in bpf-next tree, please just send a relative diff for
the selftest patch.
https://lore.kernel.org/lkml/165231901346.29050.11394051230756915389.git-patchwork-notify@kernel.org/
Thanks,
Daniel
Powered by blists - more mailing lists