All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nimit Gupta <nimit@deeproot.co.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem while using HTB bandwidth limitation
Date: Tue, 02 Sep 2003 05:51:36 +0000	[thread overview]
Message-ID: <marc-lartc-106248094615792@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106242135331948@msgid-missing>

Hello,

Thanks a lot Martin & Stef for clarifying my doubts. Your detailed 
explaination was quiet helpful in making the things clear.

I agree that if I give 24Kbit for each leaf class they will get it 
without confirming about the total bandwidth available with the parent 
but why does it allow him to reach upto 48Kbit even when ceiling is 24Kbit?

> In order for you to control
> latency and bandwidth use, you must ensure that you are the slowest point.
> Annoyingly, the only successful way to identify exactly what speed to use
> as a bandwidth cap is experimentation.  A good general suggestion is to
> lop off a couple of kbit and try capping your bandwidth exactly as Stef
> suggests.  Try using 188kbit, and see if your apparent control increases.

Is there a ratio between the total available bandwidth and the amount 
you restrict it to or you can just arbitarily reduce by 5-7 Kbit.

with regards,
Nimit.

Ps: Is there an irc channel for lartc discussion?

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

  parent reply	other threads:[~2003-09-02  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01 13:14 [LARTC] Problem while using HTB bandwidth limitation Nimit Gupta
2003-09-01 17:41 ` Stef Coene
2003-09-02  4:46 ` Martin A. Brown
2003-09-02  4:47 ` Nimit Gupta
2003-09-02  5:51 ` Nimit Gupta [this message]
2003-09-02 16:52 ` Stef Coene
2003-09-03  4:56 ` Nimit Gupta
2003-09-08 16:48 ` Stef Coene

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-106248094615792@msgid-missing \
    --to=nimit@deeproot.co.in \
    --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.