From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: pshelar@ovn.org, davem@davemloft.net, kuba@kernel.org,
azhou@ovn.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dev@openvswitch.org,
xiangxia.m.yue@gmail.com, u9012063@gmail.com,
jean.tourrilhes@hpe.com
Subject: Re: [PATCH net] openvswitch: meter: remove rate from the bucket size calculation
Date: Fri, 23 Apr 2021 20:10:28 +0000 [thread overview]
Message-ID: <161920862815.30338.13572609304102929067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210421135747.312095-1-i.maximets@ovn.org>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 21 Apr 2021 15:57:47 +0200 you wrote:
> Implementation of meters supposed to be a classic token bucket with 2
> typical parameters: rate and burst size.
>
> Burst size in this schema is the maximum number of bytes/packets that
> could pass without being rate limited.
>
> Recent changes to userspace datapath made meter implementation to be
> in line with the kernel one, and this uncovered several issues.
>
> [...]
Here is the summary with links:
- [net] openvswitch: meter: remove rate from the bucket size calculation
https://git.kernel.org/netdev/net/c/7d742b509dd7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-04-23 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 13:57 [PATCH net] openvswitch: meter: remove rate from the bucket size calculation Ilya Maximets
2021-04-23 20:10 ` patchwork-bot+netdevbpf [this message]
2021-04-28 6:24 ` Tonghao Zhang
2021-04-28 6:45 ` Jean Tourrilhes
2021-04-28 11:22 ` Ilya Maximets
2021-04-28 16:31 ` Jean Tourrilhes
2021-04-28 18:59 ` Ilya Maximets
2021-04-29 21:15 ` Ilya Maximets
2021-04-29 21:12 ` Ilya Maximets
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=161920862815.30338.13572609304102929067.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=azhou@ovn.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=i.maximets@ovn.org \
--cc=jean.tourrilhes@hpe.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=u9012063@gmail.com \
--cc=xiangxia.m.yue@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 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.