From: patchwork-bot+netdevbpf@kernel.org
To: Punit Agrawal <punit.agrawal@bytedance.com>
Cc: ast@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, zhoufeng.zf@bytedance.com,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, jolsa@kernel.org
Subject: Re: [PATCH v2] bpf: Simplify code by using for_each_cpu_wrap()
Date: Sat, 10 Sep 2022 23:30:14 +0000 [thread overview]
Message-ID: <166285261490.22663.16792763568824873547.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220907155746.1750329-1-punit.agrawal@bytedance.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 7 Sep 2022 16:57:46 +0100 you wrote:
> In the percpu freelist code, it is a common pattern to iterate over
> the possible CPUs mask starting with the current CPU. The pattern is
> implemented using a hand rolled while loop with the loop variable
> increment being open-coded.
>
> Simplify the code by using for_each_cpu_wrap() helper to iterate over
> the possible cpus starting with the current CPU. As a result, some of
> the special-casing in the loop also gets simplified.
>
> [...]
Here is the summary with links:
- [v2] bpf: Simplify code by using for_each_cpu_wrap()
https://git.kernel.org/bpf/bpf-next/c/57c92f11a215
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-09-10 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 15:57 [PATCH v2] bpf: Simplify code by using for_each_cpu_wrap() Punit Agrawal
2022-09-08 0:55 ` Song Liu
2022-09-08 10:45 ` Punit Agrawal
2022-09-08 20:21 ` Song Liu
2022-09-09 8:59 ` [External] " Punit Agrawal
2022-09-10 23:30 ` 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=166285261490.22663.16792763568824873547.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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=punit.agrawal@bytedance.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=zhoufeng.zf@bytedance.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