From: "Wingtung.Leung" <s965817@uia.ua.ac.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Priority for slower connections
Date: Fri, 08 Jun 2001 17:26:54 +0000 [thread overview]
Message-ID: <marc-lartc-99202123900620@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99164089607072@msgid-missing>
On Wed, 6 Jun 2001, Mike Fedyk wrote:
> I don't remember if TBF keeps tokens for each tcp connection seperate, but
> if it does, that may prioritize the newer connections (which means all
> connections will burst, and the bigger ones would slow down after the
> initial burst).
I think TBF itself does *not* seperate connections in a class, so new
connections in the same class will not be prioritized. I presume only the
first connection will receive a short burst time, but all other have to
live with the slow rate.
A possibility to attach a seperate TBF to each connection sounds
attractive, but on the other hand, it would request much more processing
power.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-06-08 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 7:43 [LARTC] Priority for slower connections pete
2001-06-04 8:12 ` Juergen
2001-06-04 10:45 ` Wingtung.Leung
2001-06-06 17:35 ` Mike Fedyk
2001-06-08 17:26 ` Wingtung.Leung [this message]
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-99202123900620@msgid-missing \
--to=s965817@uia.ua.ac.be \
--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.