From mboxrd@z Thu Jan  1 00:00:00 1970
From: gypsy <gypsy@iswest.com>
Date: Sat, 03 Jul 2004 04:14:24 +0000
Subject: Re: [LARTC] filter ingress policy rates -> slow!!
Message-Id: <40E632A0.51A90EE1@iswest.com>
List-Id: <lartc.vger.kernel.org>
References: <200407011810.01786.edulix@tumundoweb.com>
In-Reply-To: <200407011810.01786.edulix@tumundoweb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

Edulix wrote:
> Using 2.4.22 here (default of Fedora Core 1).
> 
> > 2) Post results of
> > grep "define PSCHED_CLOCK" /usr/src/linux/incluce/net/pkt_sched.h
> 
> # grep "define PSCHED_CLOCK" /usr/src/linux-2.4/include/net/pkt_sched.h
> #define PSCHED_CLOCK_SOURCE     PSCHED_JIFFIES
> 
> does it help ?
Yes, it sure does.

Edit pkt_sched.h and change from JIFFIES to CPU.  Before you recompile
the kernel, make config and make sure the CPU setting is higher than
CONFIG_M486 or you'll get an error message.  If you have any of the
schedule stuff (CONFIG_NET_SCH_blah) as modules (you do):

make (YourFavoriteFlavorOf)config   (checking/changing - if needed - the
CPU)
make clean ; make dep ; make bzImage
make modules
make modules_install

Those "make"s are broken up like that for a reason.  Just Do It, please.

If you did not have to change the CPU type, you can just reload the
ingress module:
modprobe -r sch_ingress
modprobe sch_ingress

and test the setup.  If you did change the CPU type, you should install
your new kernel, run lilo and reboot using the new kernel.

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