From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Tom Herbert <therbert@google.com>
Subject: Re: CPU scheduler to TXQ binding? (ixgbe vs. igb)
Date: Thu, 18 Sep 2014 20:57:25 +0200 [thread overview]
Message-ID: <20140918205725.64ddd4a7@redhat.com> (raw)
In-Reply-To: <1411058064.7106.277.camel@edumazet-glaptop2.roam.corp.google.com>
On Thu, 18 Sep 2014 09:34:24 -0700 Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Thu, 2014-09-18 at 17:59 +0200, Jesper Dangaard Brouer wrote:
> > On Thu, 18 Sep 2014 08:42:31 -0700
> > Eric Dumazet <eric.dumazet@gmail.com> wrote:
> >
[...]
> > I'm looking for some 1G hardware without multiqueue, so I can get
> > around this measurement constraint. And possibly turning it down to
> > 100Mbit/s, so I can more easily measure the HoL blocking effect.
> >
>
> ethtool -L eth0 rx 1 tx 1
>
> (Or similar if combined is used)
Thanks! - that solves my qdisc measurement problem :-)
And yes, I had to use:
ethtool -L eth1 combined 1
--
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
next prev parent reply other threads:[~2014-09-18 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:26 CPU scheduler to TXQ binding? (ixgbe vs. igb) Jesper Dangaard Brouer
2014-09-17 14:32 ` 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 [this message]
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=20140918205725.64ddd4a7@redhat.com \
--to=jbrouer@redhat.com \
--cc=alexander.h.duyck@intel.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.