All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: David Miller <davem@davemloft.net>, eric@regit.org
Cc: netdev@vger.kernel.org, xdp-newbies@vger.kernel.org,
	pmanev@stamus-networks.com,
	Alexander Duyck <alexander.duyck@gmail.com>,
	Emil Tantilov <emil.s.tantilov@intel.com>
Subject: Re: ixgbe tuning reset when XDP is setup
Date: Fri, 15 Dec 2017 08:03:01 -0800	[thread overview]
Message-ID: <c677440b-46c5-e32b-5038-21a760ba738b@gmail.com> (raw)
In-Reply-To: <20171215.105338.2092740911243038177.davem@davemloft.net>

On 12/15/2017 07:53 AM, David Miller wrote:
> From: Eric Leblond <eric@regit.org>
> Date: Fri, 15 Dec 2017 11:24:46 +0100
> 
>> 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.
> 
> This definitely should _not_ be a side effect of enabling XDP on a device.
> 

Agreed, CC Emil and Alex we should restore these settings after the
reconfiguration done to support a queue per core.

.John

  reply	other threads:[~2017-12-15 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 10:24 ixgbe tuning reset when XDP is setup Eric Leblond
2017-12-15 15:53 ` David Miller
2017-12-15 16:03   ` John Fastabend [this message]
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=c677440b-46c5-e32b-5038-21a760ba738b@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=emil.s.tantilov@intel.com \
    --cc=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 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.