Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-wpan@vger.kernel.org,
	Peter Kietzmann <peter.kietzmann@haw-hamburg.de>
Subject: Re: UDP stress-testing
Date: Tue, 12 Apr 2016 20:00:58 -0400	[thread overview]
Message-ID: <11304.1460505658@obiwan.sandelman.ca> (raw)
In-Reply-To: <57075C35.5070206@haw-hamburg.de>

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]


Peter Kietzmann <peter.kietzmann@haw-hamburg.de> wrote:
    >> Change tx queue setting:
    >>
    >> ip link set txqueuelen 1000 dev $WPAN_DEV

    > That was the parameter I was looking for. Increasing this queue it is
    > :-) !

assuming that you aren't sending packets faster than your essential bit rate,
increasing the txqueuelen just increases the latency.

A queue length of 3 or 4 ought to be enough to keep the transmitter busy.
Setting it to 1000 just causes bufferbloat.


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 464 bytes --]

  parent reply	other threads:[~2016-04-13  0:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 20:19 UDP stress-testing Peter Kietzmann
2016-04-07 20:41 ` Alexander Aring
2016-04-08  7:22   ` Peter Kietzmann
2016-04-08 12:58     ` Alexander Aring
2016-04-13  0:00     ` Michael Richardson [this message]
2016-04-13  8:28       ` Alexander Aring
2016-04-13 12:50         ` Michael Richardson
2016-04-13 20:34           ` Alexander Aring
2016-04-14  8:53             ` Peter Kietzmann
2016-04-14 14:59               ` Alexander Aring

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=11304.1460505658@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=linux-wpan@vger.kernel.org \
    --cc=peter.kietzmann@haw-hamburg.de \
    /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