netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Lin Ming <mlin@ss.pku.edu.cn>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	networking <netdev@vger.kernel.org>
Subject: Re: HTB vs CoDel performance
Date: Wed, 19 Sep 2012 10:00:32 -0700	[thread overview]
Message-ID: <5059FA30.8070209@hp.com> (raw)
In-Reply-To: <CAF1ivSYQiXBOtzZdDUKEqWWsW5cgLgSkLs88Dvkppb02yN6wTg@mail.gmail.com>

On 09/18/2012 06:26 PM, Lin Ming wrote:
> On Tue, Sep 18, 2012 at 6:15 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> Are you really cpu limited ? You might hit some clocks artifacts.
>
> Did you mean the cpu speed? It's an ARMv5 processor.
> BogoMIPS	: 1196.03

At the risk of typing into Eric's keyboard, he was asking if you were 
saturating the CPU - was it getting to 100% utilization, that sort of thing.

>> rate limiting to 1Gbps probably need high resolution timers.
>
> High resolution timer is enabled.

When you are running your tests, what sort of CPU utilization do you see 
on the CPU of your router with HTB on vs off.  Some "quick and dirty" 
netperf tests on an Centrino-based laptop suggested that as an end 
system at least, HTB at 1 GbE (using your tc commands) increases service 
demand (what netperf calculates as CPU consumed per unit of work 
performed) ~15% for bulk transfer (netperf TCP_STREAM) and ~18% for 
small packet request/response (TCP_RR).

rick jones

  reply	other threads:[~2012-09-19 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  9:28 HTB vs CoDel performance Lin Ming
2012-09-18  9:45 ` Eric Dumazet
2012-09-18  9:56   ` Lin Ming
2012-09-18 10:15     ` Eric Dumazet
2012-09-19  1:26       ` Lin Ming
2012-09-19 17:00         ` Rick Jones [this message]
2012-09-21  7:23           ` Lin Ming

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=5059FA30.8070209@hp.com \
    --to=rick.jones2@hp.com \
    --cc=eric.dumazet@gmail.com \
    --cc=mlin@ss.pku.edu.cn \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).