The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hou Tao <houtao@huaweicloud.com>
To: Yan Zhai <yan@cloudflare.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	John Fastabend <john.fastabend@gmail.com>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
	Shuah Khan <shuah@kernel.org>, Brian Vazquez <brianvv@google.com>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kernel-team@cloudflare.com
Subject: Re: [PATCH v2 bpf 2/2] selftests: bpf: test batch lookup on array of maps with holes
Date: Sat, 8 Feb 2025 09:10:44 +0800	[thread overview]
Message-ID: <b7daaf55-7d05-627b-fa12-e9d0fe87167a@huaweicloud.com> (raw)
In-Reply-To: <6e710c8034800cb14e7db2d77b2081222bcb247e.1738905497.git.yan@cloudflare.com>



On 2/7/2025 1:45 PM, Yan Zhai wrote:
> Iterating through array of maps may encounter non existing keys. The
> batch operation should not fail on when this happens.
>
> Signed-off-by: Yan Zhai <yan@cloudflare.com>

Acked-by: Hou Tao <houtao1@huawei.com>


      reply	other threads:[~2025-02-08  1:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07  5:45 [PATCH v2 bpf 0/2] bpf: skip non exist keys in Yan Zhai
2025-02-07  5:45 ` [PATCH v2 bpf 1/2] bpf: skip non exist keys in generic_map_lookup_batch Yan Zhai
2025-02-08  0:51   ` Hou Tao
2025-02-08  2:13   ` Alexei Starovoitov
2025-02-07  5:45 ` [PATCH v2 bpf 2/2] selftests: bpf: test batch lookup on array of maps with holes Yan Zhai
2025-02-08  1:10   ` Hou Tao [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=b7daaf55-7d05-627b-fa12-e9d0fe87167a@huaweicloud.com \
    --to=houtao@huaweicloud.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brianvv@google.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@cloudflare.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yan@cloudflare.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox