Re: [LARTC] Bandwidth allocation by IP

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



That sound like something what I exactly need.
    1) what is the difference (adv & disadv) between esfq and wrr?
    2) little problem in attachment, I don't know what to do. I tried latest
(that 2002-try) and latest stable version (ss010824).


> Try WRR on eth1 see http://wipl-wrr.sourceforge.net/ for details
> or use ESFQ
> see mail from Alexander Atanasov 05.06.2002
> I rename files gzip its and attach to this mail but don't change anything
> patch kernel and tc
> cd iproute2
> patch -p1 < ../esfq-tc.diff
> cd linux-2.4.18
> patch -p1 < ../esfq-2.4.18.diff
> recompile kernel and tc thats all !!
> see README
> Note it give you equal division for a long term not at the moment
> Example:
>
> tc qdisc add dev eth1 root handle 1:0 esfq hash src
>
> It make equal priority for session based on ip address not tcp session
like classic SFQ
> For detail see SFQ
> 05.06.2002 15:34:05, "Vladimir Trebicky" <druid@mail.cz> wrote:
>
> >I have a LAN (eth1) and 1Mbit internet which is very unstable (from
> >100kbit - 2mbit) on eth0. I would like to prevent ip A downloading with 9
> >threads taking 90% bandwidth and ip B downloading with 1 thread  taking
10%.
> >I would like ip A as well as ip B to have each 50% of bandwith no care
how
> >many threads they are downloading. I suppose that it could be done on
eth1.
> >But how?
> >Second problem: I want to lessen round-trips. Should I do it with
priorizing
> >small packets on eth0? How?
> >I have 2.4.18, iproute2 with extra htb. PSCHED_JIFFIES (unfortunately -
it's
> >only AMD 160MHz and does not have TSC)
> >
> >Thanks
> >
> >--
> >Vladimir Trebicky
> >druid@mail.cz
> >
> >
> >---
> >Odchozi zprava neobsahuje viry.
> >Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
> >Verze: 6.0.368 / Virová báze: 204 - datum vydání: 29.5.2002
> >
> >_______________________________________________
> >LARTC mailing list / LARTC@mailman.ds9a.nl
> >http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> >
>
> -----------------------------------
> mailto:alexey_talikov@texlab.com.uz
> BR
> Alexey Talikov
> FORTEK
> -----------------------------------
>


---
Odchozi zprava neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.368 / Virová báze: 204 - datum vydání: 29.5.2002
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -Werror -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4/include -I../include -DRESOLVE_HOSTNAMES   -c -o q_esfq.o q_esfq.c
q_esfq.c: In function `esfq_parse_opt':
q_esfq.c:45: structure has no member named `hash_kind'
q_esfq.c:45: `TCA_SFQ_HASH_CLASSIC' undeclared (first use in this function)
q_esfq.c:45: (Each undeclared identifier is reported only once
q_esfq.c:45: for each function it appears in.)
q_esfq.c:91: structure has no member named `hash_kind'
q_esfq.c:94: structure has no member named `hash_kind'
q_esfq.c:94: `TCA_SFQ_HASH_DST' undeclared (first use in this function)
q_esfq.c:97: structure has no member named `hash_kind'
q_esfq.c:97: `TCA_SFQ_HASH_SRC' undeclared (first use in this function)
q_esfq.c: In function `esfq_print_opt':
q_esfq.c:140: structure has no member named `hash_kind'
q_esfq.c:142: `TCA_SFQ_HASH_CLASSIC' undeclared (first use in this function)
q_esfq.c:145: `TCA_SFQ_HASH_DST' undeclared (first use in this function)
q_esfq.c:148: `TCA_SFQ_HASH_SRC' undeclared (first use in this function)
cc1: warnings being treated as errors
q_esfq.c:143: warning: unreachable code at beginning of switch statement
make[1]: *** [q_esfq.o] Error 1
make[1]: Leaving directory `/usr/src/iproute2/tc'
make: *** [all] Error 2

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux