netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Blizek <michi1@michaelblizek.homelinux.net>
To: netdev@vger.kernel.org
Cc: Joerg Pommnitz <pommnitz@yahoo.com>, Jarek Poplawski <jarkao2@o2.pl>
Subject: Re: Does tc-prio really work as advertised?
Date: Fri, 30 Nov 2007 19:39:46 +0100	[thread overview]
Message-ID: <20071130183946.GB2368@grml.local> (raw)
In-Reply-To: <759014.71791.qm@web51409.mail.re2.yahoo.com>

Hi!

On 05:00 Tue 27 Nov     , Joerg Pommnitz wrote:
> > So, are you still sure you've tested such a case?
> 
> Well, the problem that triggered my investigation was
> that the OLSR daemon (www.olsr.org) calculates the quality
> of a link according to the packet loss for LQ HELLO packets
> (UDP broadcast packets). To prevent other traffic from
> interfering with the LQ calculation, olsrd sends the HELLO
> packets with a TOS value of 0x10 (minimize delay). This
> should give them the highest priority.
> 
> What I saw was a degrading Link quality with more user traffic
> over a link. The LQ fell so far that olsrd judged the other host
> unreachable and deleted the routing entry. The user traffic in
> question was iperf (TOS value 0x00).
> --  
> Regards and thanks for taking an interest
> 
>  
>        Joerg

There is another possible cause of this problem.

In WLANs all packets are acked or retransmitted. This is done to
prevent packet loss due to noise and collisions. But this is not
done with broadcast packets.

I can't tell you if this can be enough to trigger the bevaviour
you experienced. Is the signal barely receivable?

Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.homelinux.net


  parent reply	other threads:[~2007-11-30 19:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 13:00 AW: Does tc-prio really work as advertised? Joerg Pommnitz
2007-11-27 14:12 ` Jarek Poplawski
2007-11-30 18:39 ` Michael Blizek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-27 13:07 Joerg Pommnitz
2007-11-27 13:18 ` Patrick McHardy
2007-11-27 10:54 AW: " Joerg Pommnitz
2007-11-27 11:58 ` Jarek Poplawski
2007-11-27 12:29   ` Patrick McHardy
2007-11-27  9:28 Joerg Pommnitz
2007-11-27  9:58 ` Jarek Poplawski
2007-11-23 14:47 Joerg Pommnitz
2007-11-26 22:25 ` Jarek Poplawski
2007-11-27  6:46   ` Jarek Poplawski

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=20071130183946.GB2368@grml.local \
    --to=michi1@michaelblizek.homelinux.net \
    --cc=jarkao2@o2.pl \
    --cc=netdev@vger.kernel.org \
    --cc=pommnitz@yahoo.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).