[Oisf-users] af_packet and rss queue count

erik clark philosnef at gmail.com
Sat Dec 24 18:28:22 UTC 2016


I will post that on Wednesday when I get back to work. Its 6? ethtool
statements, and 2 ixgbe patches (for rhel7 at least). Anything else should
be just 1 patch. This is running the 4.4.6 ixgbe released from intel
directly. This has worked for the most recent 3 kernels under RHEL7.

On Sat, Dec 24, 2016 at 12:51 PM, Peter Manev <petermanev at gmail.com> wrote:

>
>
> > On 24 Dec 2016, at 18:22, erik clark <philosnef at gmail.com> wrote:
> >
> > I have seen several places commenting that you should set the RSS queue
> to 1. However, when examining af_packet with Bro, a patch released from
> Redhat for the ixgbe kernel module, and some ethtool tweaking, we have
> found that (for Bro at least) running a full 63 (we have 54 cores) RSS
> queues vastly improves performance, and keeps state intact across sessions.
> >
> > Based on this update, which fixes the broken implementation of setting a
> symmetric hash in the hardware of the card
>
> Can you please share a bit in a bit more detail-
> Which ixgbe/kernel version that is ?
> Which patch is it ?
> What is the ethtool tweaking procedure?
>
> Thanks
>
> > (again ixgbe, not tested with i40e), is it still necessary to run one
> queue? If so, you can't run Bro and Suri on the same box with af_packet and
> get equivalent performance out of both tools. Having run Suri with 63
> queues for a week now, it seems performance is considerably better than
> with pf_ring, and I can not find any unusual behavior in my alerts...
> >
> > _______________________________________________
> > Suricata IDS Users mailing list: oisf-users at openinfosecfoundation.org
> > Site: http://suricata-ids.org | Support: http://suricata-ids.org/
> support/
> > List: https://lists.openinfosecfoundation.org/
> mailman/listinfo/oisf-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20161224/7a651b5e/attachment-0002.html>


More information about the Oisf-users mailing list