From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Proportionate sharing of excess bandwidth: still no go
Date: Fri, 01 Aug 2003 15:41:28 +0000 [thread overview]
Message-ID: <marc-lartc-105975289619490@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105974782513096@msgid-missing>
On Friday 01 August 2003 17:13, Martin A. Brown wrote:
> Hi Raj,
>
> : I tried the recommendations of people on this list and tried tweaking
> : the QUANTUM values in my HTB configuration, but still have the problem
> : of the excess bandwidth not being shared proportionately between
> : different pools.
>
> Could you tell us which interface is your "transmit to the Internet"
> interface?
>
> I speculate that you are shaping your upload bandwidth, not your download
> bandwidth. If my speculation is correct, perhaps you could try using the
> same traffic control configuration on both devices (eth0 ? and eth1).
> What happens then?
>
> : Am enclosing the set of tc commands I'm using to generate the pools.
> : The values have been desperately tweaked for some 4 hours, so some of
> : them may look a bit funny.
>
> Your quantum setting seems awfully high to me. I'd recommend removing any
> reference to quantum before trying again.
Better, remove burst, cburst and quantum.
And remove the sfq qdiscs and add 3 fifo qdiscs.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-08-01 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 14:34 [LARTC] Proportionate sharing of excess bandwidth: still no go Raj Mathur
2003-08-01 15:13 ` Martin A. Brown
2003-08-01 15:34 ` Raj Mathur
2003-08-01 15:41 ` Stef Coene [this message]
2003-08-01 15:57 ` Raj Mathur
2003-08-02 8:08 ` Stef Coene
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-105975289619490@msgid-missing \
--to=stef.coene@docum.org \
--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.