All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Qos, HFSC  and VoIP
Date: Tue, 27 Sep 2005 01:23:24 +0000	[thread overview]
Message-ID: <43389F0C.2000006@dsl.pipex.com> (raw)
In-Reply-To: <200509261832.49312.romary.sonrier@free.fr>

Romary Sonrier wrote:
> Hello, 
> I'm using Linux kernel 2.6.x and tc (from iproute2 package).
> I'm trying to use HTB or HFSC scheduler in order to limite the rate of outgoing packets and also in order to minimiez delay for RTP stream.
> But I didn't suceed in having this 2 QoS services working.
> 
> I use Iptables in order to classify packets. Here is my HFSC  conf.
> In fact the pings that i send from this box should be the most highly priorised packet, but there are delayed when i add load on the link (with a scp  upload).
> What is strange is that the delay of thoses ping is not constant:
> Does someone have an idea about this issue?

Try making the ul rates lower and see if that's it. The ping pattern 
could be because you are slightly over rate for ppp0, but when sfq 
perturbs (assuming perturb 10) the packet reordering makes the tcp back 
off enough for the queue to clear.

I know you only have sfq on ls - which is OK, but don't put sfq/prio on 
an rt or sc leaf as hfsc dequeues/requeues for these to see next packet 
length. In the case of sfq/prio it will/may not be that packet that gets 
dequeued.

I also notice your rates add up to > ul.

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

      reply	other threads:[~2005-09-27  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 16:32 [LARTC] Qos, HFSC and VoIP Romary Sonrier
2005-09-27  1:23 ` Andy Furniss [this message]

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=43389F0C.2000006@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.