From: "Vladimir Trebicky" <druid@mail.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwidth allocation by IP
Date: Wed, 05 Jun 2002 13:09:07 +0000 [thread overview]
Message-ID: <marc-lartc-102328269406200@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102327333231207@msgid-missing>
[-- 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
next prev parent reply other threads:[~2002-06-05 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 10:34 [LARTC] Bandwidth allocation by IP Vladimir Trebicky
2002-06-05 11:19 ` Alexey Talikov
2002-06-05 11:53 ` Alexander Atanasov
2002-06-05 12:03 ` Alexey Talikov
2002-06-05 13:09 ` Vladimir Trebicky [this message]
2002-06-05 13:48 ` Alexey Talikov
2002-06-05 15:07 ` Alexander Atanasov
2002-06-05 16:50 ` Martin Devera
2002-06-05 17:47 ` Vladimir Trebicky
2002-06-05 18:55 ` Vladimir Trebicky
2002-06-05 23:47 ` Alexander Atanasov
2002-06-06 9:35 ` Vladimir Trebicky
2002-06-06 22:15 ` Alexander Atanasov
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=marc-lartc-102328269406200@msgid-missing \
--to=druid@mail.cz \
--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.