From: patchwork-bot+netdevbpf@kernel.org
To: Usama Arif <usama.arif@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
ihor.solodrai@linux.dev, jolsa@kernel.org,
justinstitt@google.com, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, martin.lau@linux.dev, memxor@gmail.com,
morbo@google.com, nathan@kernel.org, ndesaulniers@google.com,
song@kernel.org, yonghong.song@linux.dev, yatsenko@meta.com,
kernel-team@meta.com
Subject: Re: [PATCH] bpf: local_storage: avoid redundant IRQ save on bucket locks
Date: Wed, 16 Sep 2026 20:00:04 +0000 [thread overview]
Message-ID: <178958880489.3266611.6236994598638968517.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916181001.201787-1-usama.arif@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 16 Sep 2026 11:10:01 -0700 you wrote:
> bpf_local_storage_update() takes the map bucket lock while holding
> local_storage->lock. bpf_selem_unlink_map() does the same; its only
> caller holds local_storage->lock. The outer lock is acquired with
> raw_res_spin_lock_irqsave(), so interrupts are already disabled at both
> sites.
>
> Using raw_res_spin_lock_irqsave() for the nested lock saves the already
> disabled IRQ state and issues another IRQ disable. The matching unlock
> tests that saved state before leaving interrupts disabled. On x86-64,
> this adds a pushfq/popq/cli sequence and a test/branch around an
> unreachable sti to each acquisition.
>
> [...]
Here is the summary with links:
- bpf: local_storage: avoid redundant IRQ save on bucket locks
https://git.kernel.org/bpf/bpf-next/c/10c4f610b215
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:[~2026-09-16 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 18:10 Usama Arif
2026-09-16 18:22 ` Kumar Kartikeya Dwivedi
2026-09-16 18:30 ` Amery Hung
2026-09-16 19:20 ` Usama Arif
2026-09-16 19:22 ` Usama Arif
2026-09-16 19:29 ` Amery Hung
2026-09-16 20:00 ` 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=178958880489.3266611.6236994598638968517.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=song@kernel.org \
--cc=usama.arif@linux.dev \
--cc=yatsenko@meta.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
all inboxes | Powered by JetHome®