All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerardo Arceri <elfarto@elfarto.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with HTB (ceil being overpassed)
Date: Thu, 29 Jan 2004 21:07:12 +0000	[thread overview]
Message-ID: <opr2j2aaes4ddcy3@mail.elfarto.com.ar> (raw)
In-Reply-To: <opr2glxzfo4ddcy3@mail.elfarto.com.ar>

>
> It seems you have hit timer innacuracy issues:
> http://www.docum.org/stef.coene/qos/faq/cache/40.html
>

Recompiled the kernel with the PSCHED_CPU modification and now
tc -s -d class show dev eth1 shows that the server is capped exactly at 
312Kpbs (2500Kbit).
BUT... read below quote..

>>  From my limited experience i would say that somehow my mrtg is 
>> measuring
>> traffic well before it passes thru htb (which seems imposible from what
>> i've read). i take the measurement on the
>> iptables FORWARD chain:
>>
>> iptables -N $server_ip-in
>> iptables -N $server_ip-out
>> iptables -A $server_ip-in -j RETURN
>> iptables -A $server_ip-out -j RETURN
>> iptables -A FORWARD -s $server_ip -j $server_ip-out
>> iptables -A FORWARD -d $server_ip -j $server_ip-in
>>
>> and to make the actual measurement:
>> iptables -nvxL $server_ip-in
>> iptables -nvxL $server_ip-out
>>


That mrtg measurement still shows 412 Kbps, how could it be. doesn't seem 
plausible that iptables reads the packets before the packet scheduler, 
since it works at a lower level closer to actual hardware.
What's the explanation for this ?
Thanks in advance.!


Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

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

  parent reply	other threads:[~2004-01-29 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  0:21 [LARTC] Problems with HTB (ceil being overpassed) Gerardo Arceri
2004-01-28  2:20 ` rubens
2004-01-29 20:41 ` Gerardo Arceri
2004-01-29 21:07 ` Gerardo Arceri [this message]
2004-02-03 23:21 ` miller69

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=opr2j2aaes4ddcy3@mail.elfarto.com.ar \
    --to=elfarto@elfarto.com.ar \
    --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.