Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Marcus Blomenkamp <Marcus.Blomenkamp@epost.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] burst per connection or filter on packet numbers
Date: Sat, 23 Nov 2002 15:25:31 +0000	[thread overview]
Message-ID: <marc-lartc-103806521506823@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103799020223836@msgid-missing>

Am Freitag, 22. November 2002 23:36 schrieb Walter Haidinger:
>
> I'd like to favour beginning connections (not just the starting packets,
> but the first, say, 100 packets) _while_ there already established
> connections which prevent recharging of the htb bursts.
>
> I've already experimented with different burst/cburst settings but it did
> not give me desired behaviour.

Greetings.

You could try the WRR (weighted-round-robin) scheduler. It's not yet included 
into the standard kernel sources, so you've got to patch them. Google should 
help.

AFAIK: WRR automatically classifies packets either by their MAC addresses or 
by IP-TCP,UDP streams. On each turn every stream gets a chance to send a 
number of packets proportional to its current priority/weight. And thats the 
clue: WRR allows the streams to start with a higher priority and decrease 
it's priority automatically by the amount of traffic processed.

Marcus

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-11-23 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22 18:32 [LARTC] burst per connection or filter on packet numbers Walter Haidinger
2002-11-22 20:10 ` Stef Coene
2002-11-22 22:36 ` Walter Haidinger
2002-11-23 15:25 ` Marcus Blomenkamp [this message]
2002-11-23 15:37 ` Walter Haidinger

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-103806521506823@msgid-missing \
    --to=marcus.blomenkamp@epost.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox