All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] icmp latency question
Date: Tue, 02 May 2006 21:10:09 +0000	[thread overview]
Message-ID: <4457CAB1.8060601@andybev.com> (raw)
In-Reply-To: <c2cd58b40604210204r78ec5341qb0785e731eacd17f@mail.gmail.com>

 >> Our company's main line is quite busy the whole day and my shaping is
 >> working perfect, however even if I give icmp priority the pings still
 >> jump around quite a bit.

 > Sorry, I don't want to offend you, but your mail has been the cause for
 > the first good laugh of the day.

It may have been a stupid question, but it does raise an issue I have noticed. Even if I 
give maximum priority to SSH/ICMP, I notice that the latency does still jump around. Is 
this because I've not set up the queueing discipline very well?

For SSH I have:
tc class add dev imq0 parent 1:1 classid 1:10 htb rate 50kbit ceil 800kbit prio 1
tc qdisc add dev imq0 parent 1:10 handle 10: sfq perturb 10
tc filter add dev imq0 parent 1:0 prio 0 protocol ip handle 10 fw flowid 1:10

For other traffic I increase prio number and flowid. e.g:
tc class add dev imq0 parent 1:1 classid 1:40 htb rate 90kbit ceil 600kbit prio 4
tc qdisc add dev imq0 parent 1:40 handle 40: sfq perturb 10
tc filter add dev imq0 parent 1:0 prio 0 protocol ip handle 40 fw flowid 1:40

The parent is:
tc qdisc add dev imq0 root handle 1: htb default 40
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-05-02 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  9:04 [LARTC] icmp latency question the sew
2006-04-29 22:59 ` Sebastian Bork
2006-05-02 21:10 ` Andrew Beverley [this message]
2006-05-02 21:24 ` Jason Boxman
2006-05-06  6:46 ` Sebastian Bork
2006-05-07 23:32 ` Andrew Beverley

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=4457CAB1.8060601@andybev.com \
    --to=andy@andybev.com \
    --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.