All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xue Liu <xue.liu@dks-koeln.de>
To: ath10k@lists.infradead.org
Subject: UDP throughput problems with WDS and ath10k
Date: Wed, 23 Mar 2016 11:53:10 +0100	[thread overview]
Message-ID: <56F27596.3080506@dks-koeln.de> (raw)

Hello everyone,

Now I am doing point to point  throughput test using  and ath10k. The 
hardwares are clearfog A1 board with armada 388 and WLE900VX (QCA9880). 
The OpenWRT trunk is running on it.

At first I did UDP throughput test ( WDS AP <---> WDS Client ) with 
iperf3 server on the WDS AP. The throughput is approx 630 Mbps.  But if 
the server sends the data, the throughput will rise to 700 Mbps.  I did 
the bidirectional test for many times. The UDP data transferring from AP 
side always has 70 - 80 Mbps more throughput.

In the same situation, I did UDP throughput test between PC and WDS AP ( 
PC <---->WDS Client <----> WDS AP ) . The PC is connected with the WDS 
client via GbE port.  I have found a more interesting result. The data 
throughput is about 678 Mbps when the data is transmitted from AP to PC. 
There is almost no performance loss. But the throughput is only about 
425 Mpbs from PC to AP.

Can anyone give me some advises or some info about the reason and how to 
improve the transmitting performance from PC to AP side. Thank you.

Regards,

Xue Liu

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

             reply	other threads:[~2016-03-23 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 10:53 Xue Liu [this message]
2016-03-23 16:54 ` UDP throughput problems with WDS and ath10k Michal Kazior
2016-03-23 17:20   ` Ben Greear
2016-03-31 14:36     ` Xue Liu
2016-03-31 14:49       ` Xue Liu
2016-09-13  9:53 ` Bruno Antunes

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=56F27596.3080506@dks-koeln.de \
    --to=xue.liu@dks-koeln.de \
    --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.