From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] new perflow rate control queue
Date: Wed, 06 Apr 2005 12:29:56 +0000 [thread overview]
Message-ID: <4253D644.6060400@dsl.pipex.com> (raw)
In-Reply-To: <20050404152117.6d90635d.lark@linux.net.cn>
Wang Jian wrote:
>
> I read back your post and I think the best solution for you is use HTB +
> PRIO.
I sort of have htb setup like prio but it's more flexable.
>
> Let interactive but low rate traffic have highest priority, and let bulk
> transfer have lowest priority and constrain them using HTB.
>
> TCP itself has some fairness: slower stream get faster, and faster
> stream get slower. The sliding window is for this.
TCP can be very unfair in some cases - different window sizes/scale on
off and 56k vs broadband peer.
I am rebuilding stuff on my gateway at the moment and noticed the
iproute patch doesn't compile with gcc 2.95.3 it's fine with 3.3.
q_perflow.c: In function `perflow_print_opt':
q_perflow.c:141: parse error before `char'
q_perflow.c:142: `b1' undeclared (first use in this function)
q_perflow.c:142: (Each undeclared identifier is reported only once
q_perflow.c:142: for each function it appears in.)
make[1]: *** [q_perflow.o] Error 1
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-04-06 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 7:21 [LARTC] new perflow rate control queue Wang Jian
2005-04-04 8:51 ` Patrick McHardy
2005-04-04 9:10 ` Wang Jian
2005-04-04 11:42 ` Andy Furniss
2005-04-04 13:53 ` Wang Jian
2005-04-04 14:39 ` Wang Jian
2005-04-04 15:10 ` Andy Furniss
2005-04-04 15:23 ` Andy Furniss
2005-04-04 15:57 ` Wang Jian
2005-04-05 22:40 ` Andy Furniss
2005-04-06 4:17 ` Wang Jian
2005-04-06 12:29 ` Andy Furniss [this message]
2005-04-06 12:48 ` Wang Jian
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=4253D644.6060400@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.