All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edulix <edulix@tumundoweb.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filter ingress policy rates -> slow!!
Date: Sat, 03 Jul 2004 09:44:46 +0000	[thread overview]
Message-ID: <200407031144.46988.edulix@tumundoweb.com> (raw)
In-Reply-To: <200407011810.01786.edulix@tumundoweb.com>

El Sábado, 3 de Julio de 2004 06:14, gypsy escribió:
> 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

Thanks for the info I don't know why I'm having problems compiling the kernel 
image [1]. It looks like a linking issue or a bad module, but I doubt it's 
easy to solve. I am going to change distro in a few days so I think that 
trying to find a solution might be not worthy :-).

What's more, I haven't changed the CPU type (Athlon by default) so I'm trying 
to build modules even without having compiled successfully the kernel image.

BTW, Should I warn the Fedora devels about the JIFFIES problem?

Thanks for your time,
    Edulix.



---
[1] In the execution of 'make bzImage', I get:
----------
make[1]: Saliendo directorio `/usr/src/linux-2.4.22-1.2135.nptl/arch/i386/lib'
make[1]: Cambiando a directorio `/usr/src/linux-2.4.22-1.2135.nptl'
kallsyms pass 1
ld -m elf_i386 -T /usr/src/linux-2.4.22-1.2135.nptl/arch/i386/vmlinux.lds -e 
stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o 
init/version.o init/do_mounts.o --start-group arch/i386/kernel/kernel.o 
arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o  
drivers/acpi/acpi.o drivers/cpufreq/cpufreq.o drivers/char/char.o 
drivers/block/block.o drivers/misc/misc.o drivers/net/net.o 
drivers/char/drm/drm.o drivers/net/fc/fc.o drivers/net/appletalk/appletalk.o 
drivers/net/tokenring/tr.o drivers/net/wan/wan.o drivers/atm/atm.o 
drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/pci/driver.o 
drivers/net/pcmcia/pcmcia_net.o drivers/net/wireless/wireless_net.o 
drivers/pnp/pnp.o drivers/video/video.o drivers/net/hamradio/hamradio.o 
drivers/media/media.o drivers/md/mddev.o drivers/isdn/vmlinux-obj.o 
crypto/crypto.o drivers/sensors/sensor.o 
net/network.o /usr/src/linux-2.4.22-1.2135.nptl/arch/i386/lib/lib.a /usr/src/linux-2.4.22-1.2135.nptl/lib/lib.a /usr/src/linux-2.4.22-1.2135.nptl/arch/i386/lib/lib.a 
--end-group -o .tmp_vmlinux1
drivers/ide/idedriver.o(.text+0x17570): En la función `ide_mediactl':
: undefined reference to `get_info_ptr'
make[1]: *** [kallsyms] Error 1
make[1]: Saliendo directorio `/usr/src/linux-2.4.22-1.2135.nptl'
make: *** [vmlinux] Error 2
----------
_______________________________________________
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  9:44 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
2004-07-03  9:44 ` Edulix [this message]
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=200407031144.46988.edulix@tumundoweb.com \
    --to=edulix@tumundoweb.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.