[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1410964359.7106.229.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 17 Sep 2014 07:32:39 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Jesper Dangaard Brouer <jbrouer@...hat.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Tom Herbert <therbert@...gle.com>
Subject: Re: CPU scheduler to TXQ binding? (ixgbe vs. igb)
On Wed, 2014-09-17 at 15:26 +0200, Jesper Dangaard Brouer wrote:
> The CPU to TXQ binding behavior of ixgbe vs. igb NIC driver are
> somehow different. Normally I setup NIC IRQ-to-CPU bindings 1-to-1,
> with script set_irq_affinity [1].
>
> For forcing use of a specific HW TXQ, I normally force the CPU binding
> of the process, either with "taskset" or with "netperf -T lcpu,rcpu".
>
> This works fine with driver ixgbe, but not with driver igb. That is
> with igb, the program forced to specific CPU, can still use another
> TXQ. What am I missing?
>
>
> I'm monitoring this with both:
> 1) watch -d sudo tc -s -d q ls dev ethXX
> 2) https://github.com/ffainelli/bqlmon
>
> [1] https://github.com/netoptimizer/network-testing/blob/master/bin/set_irq_affinity
Have you setup XPS ?
echo 0001 >/sys/class/net/ethX/queues/tx-0/xps_cpus
echo 0002 >/sys/class/net/ethX/queues/tx-1/xps_cpus
echo 0004 >/sys/class/net/ethX/queues/tx-2/xps_cpus
echo 0008 >/sys/class/net/ethX/queues/tx-3/xps_cpus
echo 0010 >/sys/class/net/ethX/queues/tx-4/xps_cpus
echo 0020 >/sys/class/net/ethX/queues/tx-5/xps_cpus
echo 0040 >/sys/class/net/ethX/queues/tx-6/xps_cpus
echo 0080 >/sys/class/net/ethX/queues/tx-7/xps_cpus
Or something like that, depending on number of cpus and TX queues.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists