All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iñaki Pascual" <ipascual@cttc.cat>
To: ath10k@lists.infradead.org
Subject: high RTT in 40 MHz channel width
Date: Fri, 29 Apr 2016 19:12:43 +0200	[thread overview]
Message-ID: <5723960B.9040404@cttc.cat> (raw)

Hi,

I am measuring TCP and UDP latency (actually RTT) and I am getting too 
high values when working with channels with 40MHz (also with 80MHz) width.

I am using hping3 for testing and these are the RTT avg values:

BW 20 MHz: TCP 0.9 UDP 1.1
BW 40 MHz: TCP 7.7 UDP 1.3
BW 80 MHz: TCP 3.5 UDP 1.3

I have tried different channels with similar results. According hping 
there are no packet loss and with wireshark I don't see any retransmission.

I am using:
driver: ath10k_pci
version: 4.2.0+
firmware-version: 10.1.467-ct-com-full-014-96d543

Any ideas?

Bests,

Iñaki

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2016-04-29 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 17:12 Iñaki Pascual [this message]
2016-04-30 16:39 ` high RTT in 40 MHz channel width Jose Núñez-Martínez (CTTC)
2016-04-30 16:50   ` Ben Greear
2016-05-05 10:36     ` Iñaki Pascual
2016-05-05 10:47 ` Michal Kazior
2016-05-05 11:05   ` Iñaki Pascual

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=5723960B.9040404@cttc.cat \
    --to=ipascual@cttc.cat \
    --cc=ath10k@lists.infradead.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.