From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, andrii@kernel.org,
song@kernel.org, haoluo@google.com, yhs@fb.com, ast@kernel.org,
daniel@iogearbox.net, kpsingh@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v3] bpf: Pass map file to .map_update_batch directly
Date: Thu, 17 Nov 2022 16:20:16 +0000 [thread overview]
Message-ID: <166870201672.18267.1764531191690477448.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116075059.1551277-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 16 Nov 2022 15:50:58 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Currently bpf_map_do_batch() first invokes fdget(batch.map_fd) to get
> the target map file, then it invokes generic_map_update_batch() to do
> batch update. generic_map_update_batch() will get the target map file
> by using fdget(batch.map_fd) again and pass it to
> bpf_map_update_value().
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf: Pass map file to .map_update_batch directly
https://git.kernel.org/bpf/bpf-next/c/3af43ba4c601
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-17 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 7:50 [PATCH bpf-next v3] bpf: Pass map file to .map_update_batch directly Hou Tao
2022-11-16 23:41 ` Yonghong Song
2022-11-17 16:20 ` patchwork-bot+netdevbpf [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=166870201672.18267.1764531191690477448.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@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=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 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.