Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Björn Snippe" <bjoern@snippe.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] share 2Mbit between 90 users - what's sensible?
Date: Mon, 27 Jan 2003 09:15:40 +0000	[thread overview]
Message-ID: <marc-lartc-104365901027073@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104359772213086@msgid-missing>

S Mohan schrieb:
> wondershaper has a set of rules for this. Why not borrow those rules and
> implement them?
> 
> Mohan

I know and will doubtless, shamelessly borrow them :) (Thanks, Bert!)
ESFQ and WRR (as suggested by Jason and Torge) both sound interesting, 
so I will stop now an try them :)
Thanks to you all,

Björn

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

      parent reply	other threads:[~2003-01-27  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26 16:13 [LARTC] share 2Mbit between 90 users - what's sensible? Björn Snippe
2003-01-26 17:18 ` Jason Tackaberry
2003-01-27  5:40 ` S Mohan
2003-01-27  9:15 ` Björn Snippe [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-104365901027073@msgid-missing \
    --to=bjoern@snippe.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