[LARTC] filter ingress policy rates -> slow!!

[Edulix]

El S=E1bado, 3 de Julio de 2004 13:09, Ed Wildgoose escribi=F3:
> >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:=20
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=20
something wrong must be happening :-).=20

> >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 =3D). BTW, I've been compiling (successfully most of the ti=
me)=20
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 curiou=
s=20
about the PSCHED_CLOCK_SOURCE value. Is it wrong or deprecated the default=
=20
=46edora's value (PSCHED_JIFFIES instead of PSCHED_CPU)? Or is it just that=
 you=20
have to compile your own kernel in order to get ingress rate policies worki=
ng=20
fine ?