From: Markus Reichelt <ml@mareichelt.com>
To: wireguard@lists.zx2c4.com, netdev@vger.kernel.org
Subject: Re: Wireguard head of line blocking when CPUs saturate
Date: Sun, 19 Jul 2026 22:09:35 +0200 [thread overview]
Message-ID: <20260719200935.GA5205@pc21.mareichelt.com> (raw)
In-Reply-To: <874iiyfrrh.fsf@toke.dk>
* Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> I'm sending this message to (a) see if anyone else is seeing the same
> kind of stalling, and (b) to get input on whether the explanation
> outlined above seems plausible. And, in the case of affirmative answers
> to both (a) and (b), to hopefully start a discussion on what to do about
> this :)
I don't use a wireguard setup on arm hardware, I am just brainstorming...
Given that you just use one tunnel, how about pinning wireguard to a core
and, more importantly, pin the program that causes the 'fat tcp flow' to
some other core?
What you describe must be a common problem on low performance ARM setups
running wg on openWRT (mikrotik comes to mind), so I'd have a look in that
corner of the internet also ;)
HTH
prev parent reply other threads:[~2026-07-19 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 15:56 Wireguard head of line blocking when CPUs saturate Toke Høiland-Jørgensen
2026-07-19 20:09 ` Markus Reichelt [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260719200935.GA5205@pc21.mareichelt.com \
--to=ml@mareichelt.com \
--cc=netdev@vger.kernel.org \
--cc=wireguard@lists.zx2c4.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.