From: Jakub Kicinski <kuba@kernel.org>
To: Etienne Champetier <champetier.etienne@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Multicast packet reordering
Date: Fri, 2 Dec 2022 13:39:02 -0800 [thread overview]
Message-ID: <20221202133902.7888c0ce@kernel.org> (raw)
In-Reply-To: <CAOdf3goC0eXSqdpdcq_-4wegMTBmYdK_uQOKUpjX7azvTamWDA@mail.gmail.com>
On Fri, 2 Dec 2022 15:09:13 -0500 Etienne Champetier wrote:
> > Yes, there are per-cpu queues in various places to help scaling,
> > if you don't pin the sender to one CPU and it gets moved you can
> > understandably get reordering w/ UDP (both on lo and veth).
>
> Is enabling RPS a workaround that will continue to work in the long term,
> or it just fixes this reordering "by accident" ?
For lo and veth it should continue to work.
> And I guess pinning the sender to one CPU is also important when
> sending via a real NIC, not only moving packets internally ?
Yes, for UDP with real NICs you may want to try to pin a flow
to a particular NIC queue.. somehow. Not sure how much of a problem
this is in practice.
prev parent reply other threads:[~2022-12-02 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 4:45 Multicast packet reordering Etienne Champetier
2022-12-02 13:46 ` Andrew Lunn
2022-12-02 15:32 ` Etienne Champetier
2022-12-02 18:34 ` Jakub Kicinski
2022-12-02 20:09 ` Etienne Champetier
2022-12-02 21:39 ` Jakub Kicinski [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=20221202133902.7888c0ce@kernel.org \
--to=kuba@kernel.org \
--cc=champetier.etienne@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).