[Oisf-users] Question about cpu-affinity

Michał Purzyński michalpurzynski1 at gmail.com
Mon Mar 5 07:31:06 UTC 2018

The SepTun Mark II we're about to publish should actually behave better on
non-IO friendly architectures, like AMD.

Speaking personally, this is my private opinion:

I don't see any deeper thought process about IO optimization on the AMD
side, other than increasing the throughput of every interconnect. That's
nice, but those aren't even close to being saturated, as we're wasting
cycles waiting for cache misses :/

Intel approached this problem in a much more systematic way.

On Sun, Mar 4, 2018 at 10:54 PM, Peter Manev <petermanev at gmail.com> wrote:

> On Mon, Mar 5, 2018 at 8:48 AM, Cooper F. Nelson <cnelson at ucsd.edu> wrote:
> > On 3/4/2018 10:30 PM, Peter Manev wrote:
> >> I was just tackling a similar AMD based system and can confirm the
> >> same observations/findings.
> >> AMD does not seem to have the same caching architecture indeed.
> > The "secret ingredient" of the SEPTUN build is the DDIO feature, which
> > allows the Intel NICs to copy packets directly into the L3 cache.
> >
> >>> What I ended up doing was creating a hybrid deployment that used my
> standard
> >>> HPC server build, 4 RSS queues/cores per NIC/NUMA node and
> cluster_flow to
> >>> have suri distribute flows to the remaining 56 cores in software.  The
> >>> reason I wanted to interleave the detect threads was to leverage the
> >>> Hypertransport bus to evenly distribute the load from both NICs over
> the
> >>> whole system.
> >> Seems like a good approach with the set up - is that with using the
> >> low entropy hash key?
> > Yes low entropy hash key, current kernel and bundled ixgbe driver.  In
> > general my build mission statement is to use a low-res timer (100hz),
> > virtual hugepages, IRQ coalescing and 4k/2mb blocks to move as much data
> > as possible per cpu 'tick'.  This allows better cache coherency per
> > process timeslice.
> >
> Ok cool.
> I will feedback my findings in the set up i currently am tackling  -
> although the difference is that i my case it is with a Mellanox NIC.
> --
> Regards,
> Peter Manev
> _______________________________________________
> 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
> Conference: https://suricon.net
> Trainings: https://suricata-ids.org/training/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20180304/41269fda/attachment-0002.html>

More information about the Oisf-users mailing list