From: Jonathan Morton <chromatix99@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: Traffic shaping at 10~300mbps at a 10Gbps link
Date: Mon, 7 Jun 2021 20:57:26 +0300 [thread overview]
Message-ID: <D3DEEA8B-1893-43D1-ACA6-6FB8C5002C7C@gmail.com> (raw)
In-Reply-To: <C81ACAE6-0B17-46B3-B9C8-4B56F6F937BD@gmail.com>
> On 7 Jun, 2021, at 8:28 pm, Rich Brown <richb.hanover@gmail.com> wrote:
>
> Saw this on the lartc mailing list... For my own information, does anyone have thoughts, esp. for this quote:
>
> "... when the speed comes to about 4.5Gbps download (upload is about 500mbps), chaos kicks in. CPU load goes sky high (all 24x2.4Ghz physical cores above 90% - 48x2.4Ghz if count that virtualization is on)..."
This is probably the same phenomenon that limits most cheap CPE devices to about 100Mbps or 300Mbps with software shaping, just on a bigger scale due to running on fundamentally better hardware.
My best theory to date on the root cause of this phenomenon is a throughput bottleneck between the NIC and the system RAM via DMA, which happens to be bypassed by a hardware forwarding engine within the NIC (or in an external switch chip) when software shaping is disabled. I note that 4.5Gbps is close to the capacity of a single PCIe v2 lane, so checking the topology of the NIC's attachment to the machine might help to confirm my theory.
To avoid the problem, you'll either need to shape to a rate lower than the bottleneck capacity, or eliminate the unexpected bottleneck by implementing a faster connection to the NIC that can support wire-speed transfers.
- Jonathan Morton
next prev parent reply other threads:[~2021-06-07 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210607133853.045a96d5@babalu>
2021-06-07 17:28 ` Rich Brown
2021-06-07 17:57 ` Jonathan Morton [this message]
2021-06-07 22:20 ` Toke Høiland-Jørgensen
2021-06-07 20:07 ` Jesper Dangaard Brouer
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D3DEEA8B-1893-43D1-ACA6-6FB8C5002C7C@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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