Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Adam James <ad@heliosphan.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] gypsy, and not only
Date: Sat, 28 Jan 2006 13:59:25 +0000	[thread overview]
Message-ID: <1138456765.7257.8.camel@heliosphan.kernelpanic.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0601280952240.8124@caramidaru.botosani.rdsnet.ro>

On Sat, 2006-01-28 at 09:57 +0200, brick@caramidaru.botosani.rdsnet.ro
wrote:
> i ve seen one of your replies here and i saw that you receomend 2 
> modifications in the kernel files in order to improve htb.
> first in pkt_sched.h, changing PSCHED_JIFFIES to PSCHED_CPU.
> and then, sch_htb.c, changing HYSTERESIS from 1 to 0.
> is it that simple?
> i mean i just change these here variables and i get better results?
> i ve done a search and found the first file in 3 locations. where exactly 
> do i do these modifications?

http://edseek.com/~jasonb/articles/traffic_shaping/buildkernel.html#sourceopts answers this.

Kernels newer than 2.6.8 allow you to change the clock source without
editing any source files. Look under 'Networking ---> QoS and/or fair
queueing  ---> Packet scheduler clock source (CPU cycle counter)'. 

Keep in mind that if you use any kind of CPU frequency scaling, do _not_
use PSCHED_CPU, as variable clock speeds are not taken into account.

HTH,

-- 
Adam James <ad@heliosphan.co.uk> 

PROOF OF GOD'S EXISTENCE #87:
ARGUMENT FROM BIBLICAL HISTORY
(1) Many modern historians think that there probably was somebody named
Jesus, maybe.
(2) Therefore, God exists.


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-01-28 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28  7:57 [LARTC] gypsy, and not only brick
2006-01-28 13:59 ` Adam James [this message]
2006-01-28 17:33 ` gypsy

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=1138456765.7257.8.camel@heliosphan.kernelpanic.co.uk \
    --to=ad@heliosphan.co.uk \
    --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