From: patchwork-bot+netdevbpf@kernel.org
To: Peilin Ye <yepeilin.cs@gmail.com>
Cc: stephen@networkplumber.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
peilin.ye@bytedance.com, chenyuming.junnan@bytedance.com,
ted@mostlyuseful.tech, dave.taht@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
cong.wang@bytedance.com
Subject: Re: [PATCH net] net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
Date: Sat, 18 Jun 2022 03:40:12 +0000 [thread overview]
Message-ID: <165552361272.10717.10367352534095157027.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220616234336.2443-1-yepeilin.cs@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 16 Jun 2022 16:43:36 -0700 you wrote:
> From: Peilin Ye <peilin.ye@bytedance.com>
>
> As reported by Yuming, currently tc always show a latency of UINT_MAX
> for netem Qdisc's on 32-bit platforms:
>
> $ tc qdisc add dev dummy0 root netem latency 100ms
> $ tc qdisc show dev dummy0
> qdisc netem 8001: root refcnt 2 limit 1000 delay 275s 275s
> ^^^^^^^^^^^^^^^^
>
> [...]
Here is the summary with links:
- [net] net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms
https://git.kernel.org/netdev/net/c/a2b1a5d40bd1
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-06-18 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 23:43 [PATCH net] net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms Peilin Ye
2022-06-17 3:08 ` Stephen Hemminger
2022-06-18 3:40 ` 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=165552361272.10717.10367352534095157027.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chenyuming.junnan@bytedance.com \
--cc=cong.wang@bytedance.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peilin.ye@bytedance.com \
--cc=stephen@networkplumber.org \
--cc=ted@mostlyuseful.tech \
--cc=xiyou.wangcong@gmail.com \
--cc=yepeilin.cs@gmail.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;
as well as URLs for NNTP newsgroup(s).