All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC Advanced Limiting
Date: Thu, 13 Oct 2005 19:45:37 +0000	[thread overview]
Message-ID: <200510131545.37554.jasonb@edseek.com> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB04B52C@xavier.staff.greatlakes.net>

On Thursday 13 October 2005 10:41, Eliot, Wireless and Server Administrator,  
Great Lakes Internet wrote:
> I am investigating changing our broadband bandwidth control scripts over to
> HFSC. What I would like to accomplish is this:
>
> { * DOWNLOAD *

Read the replies to the thread "shape downstream of a ppp link" as the same 
concept applies here.  It's difficult to shape ingress traffic.  You could, 
nevertheless, employ hfsc in some fashion for ingress either with IMQ or by 
attaching it to the LAN facing side of your network (pretend ingress is 
egress).

<snip>
> What is the maximum number you can use on class IDs?

0xFFF I believe.  (If it's actually 0xFFFF someone correct me.)

> How many customers should one router be able to handle with this kind of
> QoS policy?

That's going to depend on many things, one of which being packet matching.  
Were you going to use `tc filter` or, say, `iptables` matching?  For the 
former, with so many clients, others have posted they needed to use `tc 
filter` with hashtables or the performance hit was huge for thousands of `tc 
filter` rules.  (i.e. unusable.)

> With a P3 800MHz proccessor in a router, will I be able to implement this
> complex of a QoS policy and still have it handle 4,000 customers?
>
> What about 10,000?

Maybe.

> Is there any way to do triple numbering for class IDs (i.e. 1:1:2 instead
> of 1:12)?

No.

> Also, if you do not know for certain any of the answers to these questions,
> please do not make conjecture. Only answer with facts. Thank you in advance
> for any responses to this.

Excellent.  Then I'm sure you've read LARTC HOWTO and Google'd extensively 
already.

-- 

Jason Boxman
http://edseek.com/ - Linux and FOSS stuff

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-10-13 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 14:41 [LARTC] HFSC Advanced Limiting Eliot, Wireless and Server Administrator,  Great Lakes Internet
2005-10-13 19:45 ` Jason Boxman [this message]
2005-10-13 20:24 ` Eliot, Wireless and Server Administrator,  Great Lakes Internet
2005-10-13 20:57 ` Tomasz Chilinski
2005-10-14 12:53 ` Eliot, Wireless and Server Administrator,  Great Lakes Internet
2005-10-14 13:07 ` Nickola Kolev
2005-10-14 13:12 ` Tomasz Chilinski
2005-10-14 13:14 ` Eliot, Wireless and Server Administrator,  Great Lakes Internet
2005-10-14 16:18 ` Eliot, Wireless and Server Administrator,  Great Lakes Internet
2005-10-17 19:31 ` Andy Furniss
2005-10-19 10:49 ` Andy Furniss
2005-10-19 10:55 ` Andy Furniss
2005-10-20 12:54 ` Eliot, Wireless and Server Administrator,  Great Lakes Internet

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=200510131545.37554.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.