From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: brouer@redhat.com, bloat <bloat@lists.bufferbloat.net>,
"Ethy H. Brito" <ethy.brito@inexo.com.br>
Subject: Re: [Bloat] Fwd: Traffic shaping at 10~300mbps at a 10Gbps link
Date: Mon, 7 Jun 2021 22:07:35 +0200 [thread overview]
Message-ID: <20210607220735.7d4e0b4c@carbon> (raw)
In-Reply-To: <C81ACAE6-0B17-46B3-B9C8-4B56F6F937BD@gmail.com>
Hi Rich,
Quote:
> > I use one root HTB qdisc and one root (1:) HTB class.
Sounds like a classical case of lock congestion on the TC-root qdisc
lock. I have a solution using XDP here[1] combined with TC. Google
have also hit the problem, they solved it differently, specific to
their use-case.
[1] https://github.com/xdp-project/xdp-cpumap-tc
On Mon, 7 Jun 2021 13:28:10 -0400
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)..."
>
> Thanks.
>
> Rich
>
>
> > Begin forwarded message:
> >
> > From: "Ethy H. Brito" <ethy.brito@inexo.com.br>
> > Subject: Traffic shaping at 10~300mbps at a 10Gbps link
> > Date: June 7, 2021 at 12:38:53 PM EDT
> > To: lartc <lartc@vger.kernel.org>
> >
> >
> > Hi
> >
> > I am having a hard time trying to shape 3000 users at ceil speeds
> > from 10 to 300mbps in a 7/7Gbps link using HTB+SFQ+TC(filter by IP
> > hashkey mask) for a few days now tweaking HTB and SFQ parameters
> > with no luck so far.
> >
> > Everything seems right, up 4Gbps overall download speed with
> > shaping on. I have no significant packets delay, no dropped packets
> > and no high CPU average loads (not more than 20% - htop info)
> >
> > But 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) and as a consequence packets are dropped (as reported by tc
> > -s class sh ...), RTT goes above 200ms and a lots of ungry users.
> > This goes from about 7PM to 11 PM every day.
> >
> > If I turn shaping off, everything return to normality immediately
> > and peaks of not more than 5Gbps (1 second average) are observed
> > and a CPU load of about 5%. So I infer the uplink is not crowded.
> >
> >
> > I use one root HTB qdisc and one root (1:) HTB class.
> >
> > Then about 20~30 same level (1:xx) inner classes to (sort of) separate the users by region
> > And under these inner classes, goes the almost 3000 leaves (1:xxxx).
> >
> > I have one class with about 900 users and this quantity decreases
> > by the other inner classes having some of them with just one user.
> >
> > Is the way I'm using HTB+SFQ+TC suitable for this job?
> >
> > Since the script that creates the shaping environment is too long I do not post it here.
> >
> > What can I inform you guys to help me solve this?
> > Fragments of code, stats, some measurements? What?
> >
> > Thanks.
> >
> > Regards
> >
> > Ethy
>
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2021-06-07 20:07 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
2021-06-07 22:20 ` Toke Høiland-Jørgensen
2021-06-07 20:07 ` Jesper Dangaard Brouer [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
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=20210607220735.7d4e0b4c@carbon \
--to=brouer@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ethy.brito@inexo.com.br \
--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