I had added this feature for my own testing. I saw the use in suricata.yaml, but failed to notice that it was a per-interface option.  I’m using mpipe.threads to specify the number of woker threads. Is there a better way to specify that parameter?

The Tilera mPIPE processes packets for all the Ethernet ports together, so we currently load balance all packets across all workers using either static flow hashing, or dynamic flow hashing (similar to autofp).

Regards,
-Ken

From: Eric Leblond [mailto:notifications@github.com]
Sent: Wednesday, June 26, 2013 4:32 AM
To: inliniac/suricata
Cc: Kenneth Steele
Subject: Re: [suricata] Initial Tile mPIPE support (#403)


In src/runmode-tile.c:

> +    extern TmEcode ReceiveMpipeInit(void); // move this

> +

> +    RunModeInitialize();

> +

> +    /* Available cpus */

> +    uint16_t ncpus = UtilCpuGetNumProcessorsOnline();

> +

> +    TimeModeSetLive();

> +

> +    unsigned int pipe_max = 1;

> +    if (ncpus > 1)

> +        pipe_max = ncpus - 1;

> +

> +    intmax_t pipelines;

> +

> +    if (ConfGetInt("mpipe.threads", &pipelines) == 1) {

Why don't we have a per-interface value here ? config reading function shows you are looking to info under interface (like for af-packet) and here you access directly to a value.

—
Reply to this email directly or view it on GitHub<https://github.com/inliniac/suricata/pull/403/files#r4886332>.