All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS for Voip.
Date: Fri, 16 Jul 2004 16:54:56 +0000	[thread overview]
Message-ID: <200407161254.56216.jasonb@edseek.com> (raw)
In-Reply-To: <40F7F21E.7020305@opservices.com.br>

On Friday 16 July 2004 11:53, Andreas Klauer wrote:
<snip>
> At home, I have a different approach. There's just fair sharing between
> custumers (err, flatmates). Each person gets his HTB class, all HTB
> classes have the same priorities and rates, so everyone gets the same
> amount of bandwidth no matter what it's used for (p2p, www, voip, gaming).
> Prioritizing interactive over http over p2p traffic is then also done on a
> per-user basis. This way it doesn't matter to a single user what kind of
> traffic other users generates... the only guarantee there is that each
> user can get the same amount of bandwidth.

But how well does that scale?

# Default: Put stuff in class 2.

    $BIN_TC filter add dev $UC_DEV parent 1:$UC_MARK prio 100 \
                   protocol ip handle $UC_MARK fw flowid 1:$(($UC_MARK+2))

Would you want to do per user classifications to give SSH for each user a 
higher priority if you had, say, 230 users, for example?  Or would each user 
merely need to find for himself with his slice?

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

  parent reply	other threads:[~2004-07-16 16:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 15:19 [LARTC] QoS for Voip Alessandro Ren
2004-07-16 15:53 ` Andreas Klauer
2004-07-16 16:54 ` Jason Boxman [this message]
2004-07-16 17:51 ` ibro tj
2004-07-16 18:38 ` Andreas Klauer
2004-07-19 12:45 ` Alessandro Ren
2004-07-19 13:19 ` Andreas Klauer
  -- strict thread matches above, loose matches on Subject: below --
2003-11-28  8:12 [LARTC] QoS for VoIP Craig Main
2003-11-28 18:05 ` Kilian Krause
2007-09-27  2:31 ` Ming-Ching Tiew
2007-09-27 16:05 ` Santiago
2007-09-28  1:09 ` Ming-Ching Tiew
2007-09-28  2:45 ` Santiago
2007-09-28 14:07 ` Santiago
2007-10-01  1:00 ` Ming-Ching Tiew

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=200407161254.56216.jasonb@edseek.com \
    --to=jasonb@edseek.com \
    --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.