Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: DervishD <lartc@dervishd.net>
To: lartc@vger.kernel.org
Subject: [LARTC] cpufreq affects rate in, at least, htb
Date: Tue, 28 Aug 2007 07:47:38 +0000	[thread overview]
Message-ID: <20070828074738.GF17475@DervishD> (raw)

    Hi all :)

    I've tested this and having a cpufreq that slows down the CPU
affects the rate of HTB. My ondemand cpufreq governor scales down the
CPU frequency about 40% and this is more or less the slowdown the rate
suffers, 40%.

    Any known way of dealing with this without having to disable
cpufreq?

    Thanks in advance :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-08-28  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28  7:47 DervishD [this message]
2007-08-28 10:24 ` [LARTC] cpufreq affects rate in, at least, htb Andreas Mueller
2007-08-28 15:03 ` DervishD
2007-08-28 22:19 ` Adam James
2007-08-29  7:57 ` DervishD

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=20070828074738.GF17475@DervishD \
    --to=lartc@dervishd.net \
    --cc=lartc@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