From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Takshak Chahande <ctakshak@fb.com>
Cc: Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
ndixit@fb.com, Martin KaFai Lau <kafai@fb.com>,
Andrii Nakryiko <andriin@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Yonghong Song <yhs@fb.com>
Subject: Re: [PATCH bpf-next v4 2/2] selftests/bpf: handle batch operations for map-in-map bpf-maps
Date: Tue, 3 May 2022 17:13:21 -0700 [thread overview]
Message-ID: <CAADnVQJjmd4Y0aMePdO+19UMPFTLQEUo3uDN_sAYPBY9FnKi8A@mail.gmail.com> (raw)
In-Reply-To: <20220502213705.1170077-2-ctakshak@fb.com>
On Mon, May 2, 2022 at 2:37 PM Takshak Chahande <ctakshak@fb.com> wrote:
>
> This patch adds up test cases that handles 4 combinations:
> a) outer map: BPF_MAP_TYPE_ARRAY_OF_MAPS
> inner maps: BPF_MAP_TYPE_ARRAY and BPF_MAP_TYPE_HASH
> b) outer map: BPF_MAP_TYPE_HASH_OF_MAPS
> inner maps: BPF_MAP_TYPE_ARRAY and BPF_MAP_TYPE_HASH
>
> Signed-off-by: Takshak Chahande <ctakshak@fb.com>
> Acked-by: Yonghong Song <yhs@fb.com>
> ---
> .../bpf/map_tests/map_in_map_batch_ops.c | 245 ++++++++++++++++++
> 1 file changed, 245 insertions(+)
> create mode 100644 tools/testing/selftests/bpf/map_tests/map_in_map_batch_ops.c
>
> v3->v4:
> - Addressed nits; kept this map test together in map_tests/ (Yonghong, Andrii)
Looks like it's causing another test to fail in CI.
https://github.com/kernel-patches/bpf/runs/6264834580?check_suite_focus=true
prev parent reply other threads:[~2022-05-04 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:37 [PATCH bpf-next v4 1/2] bpf: Extend batch operations for map-in-map bpf-maps Takshak Chahande
2022-05-02 21:37 ` [PATCH bpf-next v4 2/2] selftests/bpf: handle " Takshak Chahande
2022-05-04 0:13 ` Alexei Starovoitov [this message]
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=CAADnVQJjmd4Y0aMePdO+19UMPFTLQEUo3uDN_sAYPBY9FnKi8A@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ctakshak@fb.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=ndixit@fb.com \
--cc=netdev@vger.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).