Re: RSS is not efficient when forwarding (ixgbe)

[Flavio Leitner <fbl@redhat.com>]

On Tue, Jul 08, 2014 at 02:32:43PM -0300, Carlos Carvalho wrote:
> Flavio Leitner (fbl@redhat.com) wrote on 8 July 2014 14:21:
>  >On Tue, Jul 08, 2014 at 02:09:13PM -0300, Carlos Carvalho wrote:
>  >> Flavio Leitner (fbl@redhat.com) wrote on 7 July 2014 21:28:
>  >>  >On Mon, Jul 07, 2014 at 04:33:24PM +0000, Skidmore, Donald C wrote:
>  >>  >> 
>  >>  >> 
>  >>  >> > 
>  >>  >> > It's a router forwarding traffic from one interface to another, so I guess it's
>  >>  >> > only the kernel. BTW, no firewall.
>  >>  >> > 
>  >>  >> > Flow Director needs to be enabled and I am using defaults.
>  >>  >> 
>  >>  >> Flow Director in ATR mode is on by default for ixgbe.  So like Tom mentioned the driver will create hash buckets for egress packets.  You could try disabling ATR and just use RSS.  Which would probably be the right thing to do any way since Flow Director isn't very useful for routing scenarios.  
>  >>  >
>  >>  >That was it.
>  >> 
>  >> We have a similar setup and similar problem. How do we disable ATR? I
>  >> tried to set ntuple off but this almost zeroed traffic. I also tried
>  >> to change rx-flow-hash but ethtool says it's not possible. The docs
>  >> say that one can disable ATR by setting AtrSampleRate to 0 but this
>  >> parameter doesn't exist in 3.14.10.
>  >> 
>  >> So, how do we disable ATR and keep RSS?
>  > 
>  >Keep in mind that this is actually 2 problems. One is enabling the
>  >NIC to receive the streams in all queues for this scenario (setting
>  >ntuple off and restarting the traffic works for me). The second problem
>  >is having all the queue interrupts spread among the CPUs. That's what
>  >does irqbalance, tuna, etc...
> 
> Spreading the interrupts among the cpus is not the issue for us. The
> problem is that the number of interrupts is *very* different among the
> irq's, so no matter how I distribute them among cores there will
> always be a few that get saturated while 70% of the machine capacity
> remains idle. Your case seems to be the extreme of ours, where all
> the flux goes to a single irq.
> 
> The problem is in how the NIC distributes traffic among the irq's in
> the router. Traffic comes almost only from a single machine and
> spreads through several thousand destinations in the internet. That's
> why I tried to set the receiving hash mode to the destination IP, but
> the NIC or driver refuses. So how do I even out the frequency of irq's?

So you see the traffic going to a few queues only and the rest is
idle, is that correct?  If so, then RSS seems to be working, but
since all the traffic comes from one server and likely one port,
maybe the hash is not good enough to distribute among all queues.
I'd try using software hashing instead of hw hashing to see if it
helps:
# ethtool -K <iface> rxhash off

or using Perfect Filters, but then it depends on the traffic's specifics.

BTW, there was a typo in my previous post, I had to turn on ntuple to
disable ATR.

fbl