All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Tom Herbert <therbert@google.com>, Eric Dumazet <eric.dumazet@gmail.com>
Subject: CPU scheduler to TXQ binding? (ixgbe vs. igb)
Date: Wed, 17 Sep 2014 15:26:53 +0200	[thread overview]
Message-ID: <20140917152653.1c824a22@redhat.com> (raw)


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

             reply	other threads:[~2014-09-17 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 13:26 Jesper Dangaard Brouer [this message]
2014-09-17 14:32 ` CPU scheduler to TXQ binding? (ixgbe vs. igb) Eric Dumazet
2014-09-17 14:55   ` Jesper Dangaard Brouer
2014-09-17 14:59   ` Alexander Duyck
2014-09-18  6:56     ` Jesper Dangaard Brouer
2014-09-18  7:28       ` Jesper Dangaard Brouer
2014-09-18 13:33       ` Eric Dumazet
2014-09-18 13:41         ` Eric Dumazet
2014-09-18 15:42           ` Eric Dumazet
2014-09-18 15:59             ` Jesper Dangaard Brouer
2014-09-18 16:34               ` Eric Dumazet
2014-09-18 18:57                 ` Jesper Dangaard Brouer
2014-09-18 16:07             ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140917152653.1c824a22@redhat.com \
    --to=jbrouer@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.