All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filter ingress policy rates -> slow!!
Date: Sat, 03 Jul 2004 04:14:24 +0000	[thread overview]
Message-ID: <40E632A0.51A90EE1@iswest.com> (raw)
In-Reply-To: <200407011810.01786.edulix@tumundoweb.com>

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/

  parent reply	other threads:[~2004-07-03  4:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 16:10 [LARTC] filter ingress policy rates -> slow!! Edulix
2004-07-01 20:40 ` Stef Coene
2004-07-02  8:36 ` Edulix
2004-07-02 14:13 ` gypsy
2004-07-03  4:14 ` gypsy [this message]
2004-07-03  9:44 ` Edulix
2004-07-03 11:09 ` Ed Wildgoose
2004-07-03 11:47 ` Edulix
2004-07-03 13:13 ` Ed Wildgoose
2004-07-03 15:02 ` gypsy
2004-07-03 22:25 ` Edulix
2004-07-04 19:47 ` 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=40E632A0.51A90EE1@iswest.com \
    --to=gypsy@iswest.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.