From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
laurent.bernaille@datadoghq.com, maciej.fijalkowski@intel.com,
toshiaki.makita1@gmail.com, eric.dumazet@gmail.com,
pabeni@redhat.com, john.fastabend@gmail.com, willemb@google.com
Subject: Re: [PATCH net-next] veth: Do not record rx queue hint in veth_xmit
Date: Thu, 06 Jan 2022 14:00:10 +0000 [thread overview]
Message-ID: <164147761061.14327.18077699517123305606.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.daniel@iogearbox.net>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 6 Jan 2022 01:46:06 +0100 you wrote:
> Laurent reported that they have seen a significant amount of TCP retransmissions
> at high throughput from applications residing in network namespaces talking to
> the outside world via veths. The drops were seen on the qdisc layer (fq_codel,
> as per systemd default) of the phys device such as ena or virtio_net due to all
> traffic hitting a _single_ TX queue _despite_ multi-queue device. (Note that the
> setup was _not_ using XDP on veths as the issue is generic.)
>
> [...]
Here is the summary with links:
- [net-next] veth: Do not record rx queue hint in veth_xmit
https://git.kernel.org/netdev/net-next/c/710ad98c363a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-06 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 0:46 [PATCH net-next] veth: Do not record rx queue hint in veth_xmit Daniel Borkmann
2022-01-06 3:22 ` John Fastabend
2022-01-06 9:00 ` Eric Dumazet
2022-01-06 12:57 ` Toshiaki Makita
2022-01-07 13:56 ` Daniel Borkmann
2022-01-10 6:52 ` Toshiaki Makita
2022-01-06 14:00 ` patchwork-bot+netdevbpf [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=164147761061.14327.18077699517123305606.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=laurent.bernaille@datadoghq.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toshiaki.makita1@gmail.com \
--cc=willemb@google.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.