From: Eric Dumazet <eric.dumazet@gmail.com>
To: "YU, Xiangning" <xiangning.yu@alibaba-inc.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 2/2] net: sched: Lockless Token Bucket (LTB) qdisc
Date: Wed, 8 Jul 2020 14:14:03 -0700 [thread overview]
Message-ID: <049a23c1-a404-60c8-9b20-1825b5319239@gmail.com> (raw)
In-Reply-To: <4835f4cb-eee0-81e7-d935-5ad85767802c@alibaba-inc.com>
On 7/8/20 9:38 AM, YU, Xiangning wrote:
> Lockless Token Bucket (LTB) is a qdisc implementation that controls the
> use of outbound bandwidth on a shared link. With the help of lockless
> qdisc, and by decoupling rate limiting and bandwidth sharing, LTB is
> designed to scale in the cloud data centers.
>
Before reviewing this patch (with many outcomes at first glance),
we need experimental data, eg how this is expected to work on a
typical host with 100Gbit NIC (multi queue), 64 cores at least,
and what is the performance we can get from it (Number of skbs per second,
on a class limited to 99Gbit)
Four lines of changelog seems terse to me.
next prev parent reply other threads:[~2020-07-08 21:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 16:38 [PATCH net-next v2 2/2] net: sched: Lockless Token Bucket (LTB) qdisc YU, Xiangning
2020-07-08 16:47 ` Randy Dunlap
2020-07-08 21:14 ` Eric Dumazet [this message]
2020-07-08 21:38 ` YU, Xiangning
2020-07-08 21:37 ` Eric Dumazet
2020-07-08 22:01 ` YU, Xiangning
2020-07-08 22:08 ` Eric Dumazet
2020-07-08 22:29 ` Eric Dumazet
2020-07-08 23:59 ` YU, Xiangning
2020-07-09 0:08 ` Eric Dumazet
2020-07-09 0:58 ` YU, Xiangning
2020-07-09 1:24 ` Eric Dumazet
2020-07-09 17:04 ` YU, Xiangning
2020-07-09 17:15 ` Eric Dumazet
2020-07-09 18:20 ` YU, Xiangning
2020-07-09 22:22 ` Eric Dumazet
2020-07-10 1:42 ` YU, Xiangning
2020-07-09 10:19 ` kernel test robot
2020-07-09 10:19 ` kernel test robot
2020-08-04 10:37 ` Maxim Mikityanskiy
2020-08-04 21:27 ` YU, Xiangning
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=049a23c1-a404-60c8-9b20-1825b5319239@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiangning.yu@alibaba-inc.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.