All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB MPU
Date: Mon, 17 May 2004 23:33:38 +0000	[thread overview]
Message-ID: <40A94BD2.8040007@dsl.pipex.com> (raw)
In-Reply-To: <40A37E1B.8060604@dsl.pipex.com>

Andy Furniss wrote:

> You can make HTB more accurate by setting HTB_HYSTERESIS to 0 in
> net/sched/sch_htb.c.
> 
> To save time - if you built HTB as a module, you can probably (well it
> worked for me) get away with editing htb.c and do
> 
> make SUBDIRS=net/sched modules
> and replacing /lib/modules/[kversion]/kernel/net/sched/htb.o with the
> new htb.o from your source tree.
> 
> If you are doing it live stop shaping and check with lsmod that modprobe
> -r gets rid (do it again if it's still there) of the old htb.o and
> reload shaping scripts.

Oops the htb.c or o should read sch_htb.c or o

Andy.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-05-17 23:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 13:54 [LARTC] HTB MPU Andy Furniss
2004-05-13 14:38 ` Andreas Klauer
2004-05-13 17:28 ` Andreas Klauer
2004-05-13 21:59 ` Jason Boxman
2004-05-14  7:05 ` Ed Wildgoose
2004-05-14  8:40 ` Andy Furniss
2004-05-14  9:55 ` Andy Furniss
2004-05-14 17:10 ` Jason Boxman
2004-05-17 22:36 ` Andy Furniss
2004-05-17 23:33 ` Andy Furniss [this message]
2004-05-20  6:29 ` Jason Boxman
2004-05-20 11:13 ` Andy Furniss
2004-05-21  8:19 ` syrius.ml
2004-05-24 20:53 ` Jason Boxman
2004-05-24 23:42 ` Ed Wildgoose
2004-05-28 18:54 ` Andy Furniss
2004-05-28 19:18 ` Jason Boxman
2004-05-28 21:49 ` Ed Wildgoose
2004-05-30  7:40 ` Andy Furniss
2004-05-30  7:49 ` Andy Furniss

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=40A94BD2.8040007@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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 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.