From: Eric Leblond <eric@regit.org>
To: netdev@vger.kernel.org, xdp-newbies@vger.kernel.org
Cc: Peter Manev <pmanev@stamus-networks.com>
Subject: ixgbe tuning reset when XDP is setup
Date: Fri, 15 Dec 2017 11:24:46 +0100 [thread overview]
Message-ID: <1513333486.28703.9.camel@regit.org> (raw)
Hello,
When using an ixgbe card with Suricata we are using the following
commands to get a symmetric hash on RSS load balancing:
./set_irq_affinity 0-15 eth3
ethtool -X eth3 hkey 6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A:6D:5A equal 16
ethtool -x eth3
ethtool -n eth3
Then we start Suricata.
In my current experiment on XDP, I have Suricata that inject the eBPF
program when starting. The consequence of that when using an ixgbe card
is that the load balancing get reset and all interrupts are reaching
the first core.
My analysis is that in the ixgbe_xdp_setup() function we call
ixgbe_setup_tc() that reset the hash tuning parameter.
If we run the affinity script and the ethtool commands after XDP is
loaded then things are going normal again. But this is not an optimal
behavior.
Is this really what is happening ? Is there a known workaround for this
issue ?
BR,
--
Eric Leblond <eric@regit.org>
next reply other threads:[~2017-12-15 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 10:24 Eric Leblond [this message]
2017-12-15 15:53 ` ixgbe tuning reset when XDP is setup David Miller
2017-12-15 16:03 ` John Fastabend
2017-12-15 16:51 ` Alexander Duyck
2017-12-15 16:56 ` Peter Manev
2018-01-25 13:09 ` Peter Manev
2018-01-25 15:07 ` Alexander Duyck
2018-02-21 20:01 ` Peter Manev
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=1513333486.28703.9.camel@regit.org \
--to=eric@regit.org \
--cc=netdev@vger.kernel.org \
--cc=pmanev@stamus-networks.com \
--cc=xdp-newbies@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).