From: Raj Mathur <raju@linux-delhi.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Proportionate sharing of excess bandwidth: still no go
Date: Fri, 01 Aug 2003 15:57:37 +0000 [thread overview]
Message-ID: <marc-lartc-105975345720217@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105974782513096@msgid-missing>
Hi Stef,
>>>>> "Stef" = Stef Coene <stef.coene@docum.org> writes:
Stef> [snip]
Stef> Better, remove burst, cburst and quantum. And remove the
Stef> sfq qdiscs and add 3 fifo qdiscs.
Can do that, but will it permit the PCs in each pool to share the
bandwidth available to that pool equitably?
Regards,
-- Raju
--
Raj Mathur raju@kandalaya.org http://kandalaya.org/
GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F
It is the mind that moves
_______________________________________________
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:57 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
2003-08-01 15:57 ` Raj Mathur [this message]
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-105975345720217@msgid-missing \
--to=raju@linux-delhi.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.