Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Add ability to pin bpf timer to calling
 CPU
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <169686242326.26391.4445179958402601494.git-patchwork-notify@kernel.org>
Date:   Mon, 09 Oct 2023 14:40:23 +0000
References: <20231004162339.200702-1-void@manifault.com>
In-Reply-To: <20231004162339.200702-1-void@manifault.com>
To:     David Vernet <void@manifault.com>
Cc:     bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
        andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
        yonghong.song@linux.dev, john.fastabend@gmail.com,
        kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
        jolsa@kernel.org, linux-kernel@vger.kernel.org,
        kernel-team@meta.com
Precedence: bulk

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed,  4 Oct 2023 11:23:37 -0500 you wrote:
> BPF supports creating high resolution timers using bpf_timer_* helper
> functions. Currently, only the BPF_F_TIMER_ABS flag is supported, which
> specifies that the timeout should be interpreted as absolute time. It
> would also be useful to be able to pin that timer to a core. For
> example, if you wanted to make a subset of cores run without timer
> interrupts, and only have the timer be invoked on a single core.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Add ability to pin bpf timer to calling CPU
    https://git.kernel.org/bpf/bpf-next/c/d6247ecb6c1e
  - [bpf-next,v2,2/2] bpf/selftests: Test pinning bpf timer to a core
    https://git.kernel.org/bpf/bpf-next/c/0d7ae0686075

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html