Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Gerhard Engleder <gerhard@engleder-embedded.com>
To: Dave Taht <dave.taht@gmail.com>,
	libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Fwd: [PATCH net-next 0/4] tsnep: Throttle irq, rotten pkts, RX buffer alloc and ethtool_get_channels()
Date: Fri, 18 Nov 2022 07:24:09 +0100	[thread overview]
Message-ID: <5486a072-c143-d865-8dba-02a8356c9434@engleder-embedded.com> (raw)
In-Reply-To: <CAA93jw5tQmRRGBBCBfE+Xz87790E5Bei8PY6mC0ey3g1o3SPTw@mail.gmail.com>

On 17.11.22 22:02, Dave Taht wrote:
> time sensitive networking is a thing. Now less sensitive. At least on
> this a53, an interrupt rate of 20us resulted in total cpu usage at a
> gbit...
> 
> Taking a 7x hit in latency tho, to reduce the cpu load, strikes me as
> a lot. dpdk would just spin-read here, vs a vs xdp.

7x less interrupts does not mean that latency is also 7x higher, but
latency will definitely be increased. A balance between CPU load and
latency need to be found here.

> "Without interrupt throttling, iperf server mode generates a CPU load of
> 100% (A53 1.2GHz). Also the throughput suffers with less than 900Mbit/s
> on a 1Gbit/s link. The reason is a high interrupt load with interrupts
> every ~20us.
> 
> Reduce interrupt load by throttling of interrupts. Interrupt delay is
> configured statically to 64us. For iperf server mode the CPU load is
> significantly reduced to ~20% and the throughput reaches the maximum of
> 941MBit/s. Interrupts are generated every ~140us."

      reply	other threads:[~2022-11-18  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221117201440.21183-1-gerhard@engleder-embedded.com>
2022-11-17 21:02 ` Dave Taht
2022-11-18  6:24   ` Gerhard Engleder [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/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5486a072-c143-d865-8dba-02a8356c9434@engleder-embedded.com \
    --to=gerhard@engleder-embedded.com \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /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