From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Niklas_S=C3=B6derlund_=3Cniklas=2Esoderlund=40corigine=2Ecom=3E?=@ci.codeaurora.org
Cc: bjorn@kernel.org, magnus.karlsson@intel.com,
jonathan.lemon@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, louis.peens@corigine.com,
simon.horman@corigine.com, bpf@vger.kernel.org,
oss-drivers@corigine.com
Subject: Re: [bpf-next] samples/bpf: xdpsock: Fix race when running for fix duration of time
Date: Tue, 15 Mar 2022 16:00:10 +0000 [thread overview]
Message-ID: <164736001078.10194.6138869870948326446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220315102948.466436-1-niklas.soderlund@corigine.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 15 Mar 2022 11:29:48 +0100 you wrote:
> When running xdpsock for a fix duration of time before terminating
> using --duration=<n>, there is a race condition that may cause xdpsock
> to terminate immediately.
>
> When running for a fixed duration of time the check to determine when to
> terminate execution is in is_benchmark_done() and is being executed in
> the context of the poller thread,
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: xdpsock: Fix race when running for fix duration of time
https://git.kernel.org/bpf/bpf-next/c/8fa42d78f635
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-03-15 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 10:29 [bpf-next] samples/bpf: xdpsock: Fix race when running for fix duration of time Niklas Söderlund
2022-03-15 16: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=164736001078.10194.6138869870948326446.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Niklas_S=C3=B6derlund_=3Cniklas=2Esoderlund=40corigine=2Ecom=3E?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jonathan.lemon@gmail.com \
--cc=louis.peens@corigine.com \
--cc=magnus.karlsson@intel.com \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.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.