All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] pfifo_fast doesn't seem to use bands
Date: Tue, 27 May 2003 01:57:18 +0000	[thread overview]
Message-ID: <marc-lartc-105405473620879@msgid-missing> (raw)

On Tuesday 27 May 2003 14:09, Balazs Miklos wrote:
> Hi,
>
> I have a Redhat Linux 7.2 box with stock 2.4.7 kernel and I'm trying to
> do some bandwidth management with tc..
> I have created a CBQ class-hierarchy, and I have a class which is
> limited to 16Kbit and it can grow up to 32Kbits if there is available
> free bandwidth in the other classes. This class hasn't got any qdiscs
> attached to it, so (as I understood) it should have the pfifo_fast qdisc
> by default. But I have made a little test: I've mangled the TOS field of
> the router's outgoing ICMP packets to be 0x10 (minimize delay), and I
> checked with tcpdump that they are actually getting mangled.
>
> The problem is, that it doesn't seem to make any difference... the ping
> is fine if the class is empty, but if I'm doing a download and pinging
> the router at the same time, I experience delays in ping replies in both
> cases (either if the ICMP headers are mangled or not). Shouldn't the TOS
> mangled ping replies arrive with no delays at all, while the class is
> full with bulk traffic?
Why not doing the test after you add a pfifo_qdisc to that class?  Just to see 
if it makes any difference.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

             reply	other threads:[~2003-05-27  1:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  1:57 Stef Coene [this message]
2003-05-27  9:49 ` [LARTC] pfifo_fast doesn't seem to use bands Balazs Miklos

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-105405473620879@msgid-missing \
    --to=stef.coene@docum.org \
    --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.