All of lore.kernel.org
 help / color / mirror / Atom feed
From: tc@forest.one.pl
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Strange pings.
Date: Sun, 24 Apr 2005 11:03:30 +0000	[thread overview]
Message-ID: <200504241303.30357.tc@forest.one.pl> (raw)
In-Reply-To: <200504200055.42395.tc@forest.one.pl>

On Friday 22 of April 2005 01:34, you wrote:
> tc@forest.one.pl wrote:
> 
> > 64 bytes from 192.168.1.1: icmp_seq• ttld time‰.0 ms
> 
> Which is about 2 packets @ 256kbit. I tested and got the same behaviour 
> with a simple setup, but max ping about 45 because htb dequeues in pairs 
> by default. If you change #define hysteresis from 1 to 0 in 
> net/sched/sch_htb.c then it's more accurate. Setting Quantum to your MTU 
> may also help.
ok. I changed hysteresis and I changed quantum.
> 
> > Then it is stable (0.4ms) for some time.
> > 
> > The same situation repeats in about 60 second delay.
> > 
> > Maybe someone solved this problem?
> 
> Give interactive class more rate than it needs. Latency was OK for me 
> with ICMP class rate 255kbit ceil 256kbit.
> 
I can't give 255 kbit to icmp traffic :) But for me 4kbit seems to be enough. 
On testing environment it works fine. But on "real" configuration
the pings are still too long. 
I wonder if one-level configuration (with just one root qdisc) would give
better latency.

> > 
> > PPS. Is it possible to create a filter that will match all packets?
> 
> I don't know about all, but all per protocol like -
> 
> .. protocol ip prio 10 u32 match u32 0 0 ..
> .. protocol arp prio 11 u32 match u32 0 0 ..
> 
It works ok for me, but only with prio 0.

Thanks for help.

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

  parent reply	other threads:[~2005-04-24 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 22:55 [LARTC] Strange pings tc
2005-04-21 23:34 ` Andy Furniss
2005-04-22 21:08 ` tc
2005-04-24 11:03 ` tc [this message]
2005-04-24 23:59 ` Andy Furniss
2005-05-13 23:36 ` Andy Furniss

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=200504241303.30357.tc@forest.one.pl \
    --to=tc@forest.one.pl \
    --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.