From: Edulix <edulix@tumundoweb.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filter ingress policy rates -> slow!!
Date: Sat, 03 Jul 2004 11:47:59 +0000 [thread overview]
Message-ID: <200407031348.00292.edulix@tumundoweb.com> (raw)
In-Reply-To: <200407011810.01786.edulix@tumundoweb.com>
El Sábado, 3 de Julio de 2004 13:09, Ed Wildgoose escribió:
> >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 :-).
>
> Unlikely to change anything... Compiling is somewhat independent of the
> rest of your system (perhaps depends on gcc version and some other
> stuff, but not too much in practice)
I think it will change because:
I'm not going to use the same distro, but change from Fedora to Suse.
What's more, I've managed to compile this same kernel source time ago, so
something wrong must be happening :-).
> >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.
>
> Aha, but did you do all the "make" commands that you were told to do?
> It's important that they are all done
Of course I did =). BTW, I've been compiling (successfully most of the time)
2.4.x linux kernels since 2-3 years ago :-P.
As I said, I'll get Suse 9.1 Prof soon (the 10th most probably). I'm curious
about the PSCHED_CLOCK_SOURCE value. Is it wrong or deprecated the default
Fedora's value (PSCHED_JIFFIES instead of PSCHED_CPU)? Or is it just that you
have to compile your own kernel in order to get ingress rate policies working
fine ?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-07-03 11:47 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
2004-07-03 11:09 ` Ed Wildgoose
2004-07-03 11:47 ` Edulix [this message]
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=200407031348.00292.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.