All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB not working quite the way I'd expect?
Date: Sun, 03 Feb 2002 20:20:03 +0000	[thread overview]
Message-ID: <marc-lartc-101276765720836@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101262785901252@msgid-missing>

> > Simply add prio 1 to the class definition (last tc line above).
> > And let me know ! ;)
> 
> In fact, there is no change.  Here is my current configuration, with the
> changes you suggested:
> 
>       ceil 200kbps burst 2k prio 4

default max prio is 3 by the way but it is not problem here ..

> Monitoring eth8, I see it sending out at 200k/s, all traffic generated
> from 199.212.55.128/25.  This is what I'd expect.  When I hit the
> webserver (on 199.212.53.0/24) hard, eth8 begins to send at 250k/s (it
> is a 2Mbit uplink), but the portion of that from the webserver is only
> about 50-90/s, not 200k/s like I'd expect based on id 1:10.

very interesting ! I'm interested in "tc -s -d class show dev eth8" output
in middle of your run. Please take several snapshots, copy into file along
with time (I need to know the time difference between them).
I'll look at them and try to deduce the problem. I use configuration like
your regulary with no probs so that I'm really interested.

devik

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

  parent reply	other threads:[~2002-02-03 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02  5:32 [LARTC] HTB not working quite the way I'd expect? Jason Tackaberry
2002-02-02 13:14 ` Martin Devera
2002-02-03 19:41 ` Jason Tackaberry
2002-02-03 20:20 ` Martin Devera [this message]
2002-02-03 21:01 ` Jason Tackaberry
2002-02-03 21:11 ` Jason Tackaberry
2002-02-03 22:25 ` Martin Devera
2002-02-03 22:37 ` Jason Tackaberry
2002-02-04  7:01 ` Martin Devera
2002-02-04 15:04 ` Jason Tackaberry

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-101276765720836@msgid-missing \
    --to=devik@cdi.cz \
    --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.