All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kietzmann <peter.kietzmann@haw-hamburg.de>
To: linux-wpan@vger.kernel.org
Subject: UDP stress-testing
Date: Thu, 7 Apr 2016 22:19:35 +0200	[thread overview]
Message-ID: <5706C0D7.1040000@haw-hamburg.de> (raw)

Dear list,

first of all let me say that I'm new to this list. So if I'm completely 
wrong in my concern please excuse the noise and guide me to the right 
place. If you can :-)!

For some experiments I'm trying to send "great" numbers of UDP packets 
with "great" payloads as fast as possible from a RasPi equipped with the 
Openlabs transceiver. With another RasPi+transceiver I'm sniffing the 
traffic. It turns out that just the first x packets are sent out 
correctly before the outgoing packets come out irregularly. The number 
of correctly sent packets depends on the UDP payload size and it looks 
like the problem occurs after ~30-35 kB Bytes (gross) in total have been 
transmitted (fragmentation overhead included). I already increased the 
send socket memory to a reasonably high value, without success. But 
still I assume some buffer problems. Do you have a hint which screw to 
adjust?

BTW: Introducing a delay after each packet to send fixes the problem. 
But I'd like to do stress-testing...

Best
Peter

-- 
Peter Kietzmann

Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49-40-42875-8426
Web: http://www.haw-hamburg.de/inet

             reply	other threads:[~2016-04-07 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 20:19 Peter Kietzmann [this message]
2016-04-07 20:41 ` UDP stress-testing Alexander Aring
2016-04-08  7:22   ` Peter Kietzmann
2016-04-08 12:58     ` Alexander Aring
2016-04-13  0:00     ` Michael Richardson
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=5706C0D7.1040000@haw-hamburg.de \
    --to=peter.kietzmann@haw-hamburg.de \
    --cc=linux-wpan@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.