From: Aleksei Zakharov <zakharov.a.g@yandex.ru>
To: netdev@vger.kernel.org
Subject: RPS arp processing
Date: Wed, 11 Dec 2019 18:26:06 +0300 [thread overview]
Message-ID: <83161576077966@vla4-87a00c2d2b1b.qloud-c.yandex.net> (raw)
Hi, everyone
Is it possible to balance ARP across CPUs with RPS?
I don't clearly understand how hash is calulated for ARP packets, but it seems that it should consider source and target IPs.
In our current setup we have one l2 segment between external hardware routers and namespaces on linux server.
When router sends ARP request, it is passed through server's physical port, then via openvswitch bridge it is copied to every namespace.
We've found that all ARPs (for different destination ips and few source ips) are processed on one CPU inside namespaces. We use RPS, and most packets are balanced between all CPUs.
Kernel 4.15.0-65 from ubuntu 18.04.
Might this issue be related to namespaces somehow?
--
Regards,
Aleksei Zakharov
next reply other threads:[~2019-12-11 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 15:26 Aleksei Zakharov [this message]
2019-12-11 18:59 ` RPS arp processing Willem de Bruijn
2019-12-11 22:08 ` Aleksei Zakharov
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=83161576077966@vla4-87a00c2d2b1b.qloud-c.yandex.net \
--to=zakharov.a.g@yandex.ru \
--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).