From: patchwork-bot+netdevbpf@kernel•org
To: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Cc: naresh.kamboju@linaro•org, netdev@vger•kernel.org,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
lkft-triage@lists•linaro.org, davem@davemloft•net,
kuba@kernel•org, jhs@mojatatu•com, xiyou.wangcong@gmail•com,
jiri@resnulli•us, tglx@linutronix•de, a.darwish@linutronix•de
Subject: Re: [PATCH net-next] net: stats: Read the statistics in ___gnet_stats_copy_basic() instead of adding.
Date: Thu, 21 Oct 2021 11:50:18 +0000 [thread overview]
Message-ID: <163481701891.17414.17028188432816254517.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211021095919.bi3szpt3c2kcoiso@linutronix.de>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 21 Oct 2021 11:59:19 +0200 you wrote:
> Since the rework, the statistics code always adds up the byte and packet
> value(s). On 32bit architectures a seqcount_t is used in
> gnet_stats_basic_sync to ensure that the 64bit values are not modified
> during the read since two 32bit loads are required. The usage of a
> seqcount_t requires a lock to ensure that only one writer is active at a
> time. This lock leads to disabled preemption during the update.
>
> [...]
Here is the summary with links:
- [net-next] net: stats: Read the statistics in ___gnet_stats_copy_basic() instead of adding.
https://git.kernel.org/netdev/net-next/c/c5c6e589a8c8
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:[~2021-10-21 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:39 [Next] WARNING: CPU: 1 PID: 219 at include/linux/seqlock.h:271 gnet_stats_add_basic+0x2e0/0x548 Naresh Kamboju
2021-10-21 9:59 ` [PATCH net-next] net: stats: Read the statistics in ___gnet_stats_copy_basic() instead of adding Sebastian Andrzej Siewior
2021-10-21 11:50 ` 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=163481701891.17414.17028188432816254517.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=a.darwish@linutronix$(echo .)de \
--cc=bigeasy@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tglx@linutronix$(echo .)de \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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