lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 17 Sep 2014 15:26:53 +0200 From: Jesper Dangaard Brouer <jbrouer@...hat.com> To: "netdev@...r.kernel.org" <netdev@...r.kernel.org> Cc: Tom Herbert <therbert@...gle.com>, Eric Dumazet <eric.dumazet@...il.com> Subject: CPU scheduler to TXQ binding? (ixgbe vs. igb) 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 -- Best regards, Jesper Dangaard Brouer MSc.CS, Sr. Network Kernel Developer at Red Hat Author of http://www.iptv-analyzer.org LinkedIn: http://www.linkedin.com/in/brouer -- 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