CoreXl tuning

[Marco_Valenti]

Hey expert

I have a doubt about splitting corexl between fw worker and snd/irq cores.

Before starting tuning I have a situation like that , 32 virtual core (ht enabled) 28 fwworker 4snd/irq , since we are going to use only one bond of two 10gb interfaces I was thinking to increment snd/irq core to 6 going 26 fw worker.

My question is do I need to use sim affinity -s and assign the new snd/irq cores to the interfaces used for the bond interface  or since all other interfaces are down this configuration is not needed and sim affinity -a is enough?

Thanks

[Marco_Valenti]

bump

[PhoneBoy]

I tend to stick with defaults until they don't work.

But if you're concerned, you might as well double-check the affinity.

[Marco_Valenti]

so " sim affinity -a " will be the best option at the moment

[Timothy_Hall]

Automatic interface affinity (sim affinity -a) is the default.  With 2 10gig interfaces a starting split of 6/24 is quite reasonable; if there is a large amount of fully-accelerated traffic you might need more SNDs than that. 

If there will only be two main interfaces used and they will handle almost all the traffic, Multi-Queue might be prudent as well depending on network traffic load and the burstiness level of network traffic.

--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com

[Marco_Valenti]

Thanks for the reply Tim , so basically I can leave the other interface in shut and there are no need so assign the other snd/irq core to the 2 gb interface with sim affinity -s command

[Timothy_Hall]

No just let automatic interface affinity handle it and enable Multi-Queue.

--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com