[LARTC] Bandwidth allocation by IP

[LARTC] Bandwidth allocation by IP

[Vladimir Trebicky]

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/

Re: [LARTC] Bandwidth allocation by IP

[Alexey Talikov]

[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]

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
-----------------------------------

[-- Attachment #2: esfq.tar.gz --]
[-- Type: application/x-gzip, Size: 7054 bytes --]

Re: [LARTC] Bandwidth allocation by IP

[Alexander Atanasov]

	Hi there!

On Wed, 05 Jun 2002 16:19:41 +0500
"Alexey Talikov" <alexey_talikov@texlab.com.uz> wrote:

> I rename files gzip its and attach to this mail but don't change
> anything patch kernel and tc

	I'll put them somewhere on the web tonight and provide an url.

> 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 

	Note that sfq is on egress and client IPs are destinations, not sources,
so you should use dst hash to divide bandwidth between clients, if you use src hash you have equal priority on server flows not on clients ones: client A downloads from server X and from server Y, client B downloads from server Z - you have bandwidth devided to X:Y:Z, not A:B, since downloads are coming from X/Y/Z(source) to A/B(destination).
	
--
have fun,
alex
P.S. Thank you for the feedback and trying it. :)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Alexey Talikov]

Thanks for your note about my error !!
You right needed dst ip but I write src :((
 
05.06.2002 16:53:29, Alexander Atanasov <alex@ssi.bg> wrote:

>	Hi there!
>
>On Wed, 05 Jun 2002 16:19:41 +0500
>"Alexey Talikov" <alexey_talikov@texlab.com.uz> wrote:
>
>> I rename files gzip its and attach to this mail but don't change
>> anything patch kernel and tc
>
>	I'll put them somewhere on the web tonight and provide an url.
>
>> 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 
>
>	Note that sfq is on egress and client IPs are destinations, not sources,
>so you should use dst hash to divide bandwidth between clients, if you use src hash you have equal 
priority on server flows not on clients ones: client A downloads from server X and from server Y, 
client B downloads from server Z - you have bandwidth devided to X:Y:Z, not A:B, since downloads 
are coming from X/Y/Z(source) to A/B(destination).
>	
>--
>have fun,
>alex
>P.S. Thank you for the feedback and trying it. :)
>

-----------------------------------
mailto:alexey_talikov@texlab.com.uz
BR
Alexey Talikov
FORTEK
-----------------------------------


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Vladimir Trebicky]

[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]

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

[-- Attachment #2: error.txt --]
[-- Type: text/plain, Size: 1350 bytes --]

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

Re: [LARTC] Bandwidth allocation by IP

[Alexey Talikov]

use latest version iproute2-2.4.7-now-ss020116-try
it work without problem (for me)
esfq is more simple in configuration that wrr 
but in wrr more features for traffic control
and its use another principle
read more about WRR and also see doc in package wrr and
see http://docum.org/. 

05.06.2002 18:09:07, "Vladimir Trebicky" <druid@mail.cz> wrote:

>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
>
>

-----------------------------------
mailto:alexey_talikov@texlab.com.uz
BR
Alexey Talikov
FORTEK
-----------------------------------


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Alexander Atanasov]

On Wed, 5 Jun 2002 15:09:07 +0200
"Vladimir Trebicky" <druid@mail.cz> wrote:

> 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).
> 

	You're tring to build tc without kernel patch applied or with a different
kernel source tree . Check is kernel patched  and then check:
iproute2/Makefile:
KERNEL_INCLUDE=/usr/src/linux/include

If your patched kernel is elsewhere change this to point there and then "make clean; make".

--
have fun,
alex
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Martin Devera]

ESFQ !? Did I missed something ? :-)
devik

On Wed, 5 Jun 2002, Alexey Talikov wrote:

> use latest version iproute2-2.4.7-now-ss020116-try
> it work without problem (for me)
> esfq is more simple in configuration that wrr
> but in wrr more features for traffic control
> and its use another principle
> read more about WRR and also see doc in package wrr and
> see http://docum.org/.
>
> 05.06.2002 18:09:07, "Vladimir Trebicky" <druid@mail.cz> wrote:
>
> >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
> >
> >
>
> -----------------------------------
> mailto:alexey_talikov@texlab.com.uz
> BR
> Alexey Talikov
> FORTEK
> -----------------------------------
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Vladimir Trebicky]

[-- Attachment #1: Type: text/plain, Size: 3039 bytes --]

I've compiled tc (after hint to patch the kernel first :-) and also kernel.
Both with extra wrr, esfq and htb. I forgot to ask whether is esfq supposed
to be compiled as a module or to be built-in. So I've tried it as built-in
and after command tc qdisc add dev eth1 root handle 1: esfq hash src:
RNETLING answers: Invalid argument
That seems to me like it wouldn't be in kernel, but it is :-(
Please see my configuration for kernel in attachment.
Somewhere there is also something that does that my machine has address
like: mymachine.IN-ADDR-ARPA... I don't know what it is and I also don't
want to uncheck something I could possibly need for Full-NAT and QoS...

----- Original Message -----
From: "Alexey Talikov" <alexey_talikov@texlab.com.uz>
To: <lartc@mailman.ds9a.nl>; "Vladimir Trebicky" <druid@mail.cz>
Sent: Wednesday, June 05, 2002 1:19 PM
Subject: Re: [LARTC] Bandwidth allocation by IP


> 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

[-- Attachment #2: shotek --]
[-- Type: application/octet-stream, Size: 15547 bytes --]

#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_USE_STRING_486=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_PPRO_FENCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_SMP is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set

#
# General setup
#
CONFIG_NET=y
# CONFIG_PCI is not set
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_PM is not set
# CONFIG_ACPI is not set
# CONFIG_APM is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_LOOP is not set
CONFIG_BLK_DEV_NBD=y
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_LARGE_TABLES=y
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_INET_ECN=y
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_FTP=y
CONFIG_IP_NF_IRC=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_MATCH_LIMIT is not set
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
# CONFIG_IP_NF_MATCH_AH_ESP is not set
CONFIG_IP_NF_MATCH_LENGTH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_STATE=y
# CONFIG_IP_NF_MATCH_UNCLEAN is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
# CONFIG_IP_NF_TARGET_MIRROR is not set
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=y
CONFIG_IP_NF_NAT_FTP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_LOG=y
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_IP_NF_TARGET_TCPMSS=y
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_CSZ=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_WRR=m
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_ESFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_IDE_MODES is not set
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_ISA=y
# CONFIG_E2100 is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_LP486E is not set
# CONFIG_ETH16I is not set
CONFIG_NE2000=y
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set

#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_I810=y
CONFIG_AGP_VIA=y
CONFIG_AGP_AMD=y
CONFIG_AGP_SIS=y
CONFIG_AGP_ALI=y
# CONFIG_AGP_SWORKS is not set
CONFIG_DRM=y
# CONFIG_DRM_OLD is not set
CONFIG_DRM_NEW=y
CONFIG_DRM_TDFX=y
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_JBD_DEBUG is not set
# CONFIG_FAT_FS is not set
# CONFIG_MSDOS_FS is not set
# CONFIG_UMSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set
# CONFIG_ZLIB_FS_INFLATE is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
# CONFIG_NLS is not set

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VIDEO_SELECT is not set
# CONFIG_MDA_CONSOLE is not set

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set
# CONFIG_USB_UHCI is not set
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_RIO500 is not set

#
# Bluetooth support
#
# CONFIG_BLUEZ is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_BUGVERBOSE=y

Re: [LARTC] Bandwidth allocation by IP

[Vladimir Trebicky]

Sorry for my incompetence. I didn't noticed that readme included in some of
Alexes posts. Module works fine only if I do
qdisc add dev eth1 root handle 1: esfq
when I do
qdisc add dev eth1 root handle 1: esfq hash dst
the computer get totally freezed.

----- Original Message -----
From: "Alexey Talikov" <alexey_talikov@texlab.com.uz>
To: <lartc@mailman.ds9a.nl>; "Vladimir Trebicky" <druid@mail.cz>
Sent: Wednesday, June 05, 2002 1:19 PM
Subject: Re: [LARTC] Bandwidth allocation by IP


> 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

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Alexander Atanasov]

	Hi there!

On Wed, 5 Jun 2002, Vladimir Trebicky wrote:

> Sorry for my incompetence. I didn't noticed that readme included in some of
> Alexes posts. Module works fine only if I do
> qdisc add dev eth1 root handle 1: esfq
> when I do
> qdisc add dev eth1 root handle 1: esfq hash dst
> the computer get totally freezed.
> 

	Are you sure you've build the kernel correct?

	I've fixed some things about default parameters - i think you've
hit this, hash_divisor was left to be 0 when not supplied as parameter.
	Now works and as built in - forgot to include sch_api.c when
making diff first time, so it was in kernel but not registerd.
	I've setup a page for it on: http://www.ssi.bg/~alex/esfq/index.html
	
-- 
have fun,
alex

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Bandwidth allocation by IP

[Vladimir Trebicky]

Well, I took 0.2 version, I compiled it as a module - no problem.
tc qdisc add dev eth1 root handle 1: esfq hash dst
- ok
but then I started in one moment to upload (via eth1 of course) 3 scp's. The
first 2 were uploading on ip A and the third was uploading on ip B. But all
those three threads were uploading with eqaul rate. Either I missed
something (it's not so rare) or something went wrong...

what do you thing?

root:/usr/src# tc -s qdisc show dev eth1
qdisc esfq 1: quantum 1514b hash: dst
 Sent 5615415 bytes 4513 pkts (dropped 0, overlimits 0)


----- Original Message -----
From: "Alexander Atanasov" <alex@ssi.bg>
To: "Vladimir Trebicky" <druid@mail.cz>
Cc: <alexey_talikov@texlab.com.uz>; <lartc@mailman.ds9a.nl>
Sent: Thursday, June 06, 2002 4:47 AM
Subject: Re: [LARTC] Bandwidth allocation by IP


> Hi there!
>
> On Wed, 5 Jun 2002, Vladimir Trebicky wrote:
>
> > Sorry for my incompetence. I didn't noticed that readme included in some
of
> > Alexes posts. Module works fine only if I do
> > qdisc add dev eth1 root handle 1: esfq
> > when I do
> > qdisc add dev eth1 root handle 1: esfq hash dst
> > the computer get totally freezed.
> >
>
> Are you sure you've build the kernel correct?
>
> I've fixed some things about default parameters - i think you've
> hit this, hash_divisor was left to be 0 when not supplied as parameter.
> Now works and as built in - forgot to include sch_api.c when
> making diff first time, so it was in kernel but not registerd.
> I've setup a page for it on: http://www.ssi.bg/~alex/esfq/index.html
>
> --
> have fun,
> alex
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


---
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/

Re: [LARTC] Bandwidth allocation by IP

[Alexander Atanasov]

On Thu, 6 Jun 2002, Vladimir Trebicky wrote:

> Well, I took 0.2 version, I compiled it as a module - no problem.
> tc qdisc add dev eth1 root handle 1: esfq hash dst
> - ok
> but then I started in one moment to upload (via eth1 of course) 3 scp's. The
> first 2 were uploading on ip A and the third was uploading on ip B. But all
> those three threads were uploading with eqaul rate. Either I missed
> something (it's not so rare) or something went wrong...
> 
> what do you thing?

	You attached esfq as your root qdisc it have 10/100MBits
bandwidth. 3 SCPs can hardly fill up a 10/100MBits link - each
one should send data 3.33/33.3MBits , i guess they send less.

-- 
have fun,
alex

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/