All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Here are some ath10k performance graphs.
Date: Sun, 30 Mar 2014 23:27:48 -0700	[thread overview]
Message-ID: <53390AE4.4030705@candelatech.com> (raw)

I finally have a firmware stable enough to do some throughput
tests (only locked station machine up once doing these!).

I find the download test interesting where the rx link rate goes very low
after 12 or so stations.

tx link rate is not reported properly yet by ath10k, so ignore that.

http://www.candelatech.com/examples/cap-ath10k-tcp-download-open/
http://www.candelatech.com/examples/cap-ath10k-tcp-download-wpa2/
http://www.candelatech.com/examples/cap-ath10k-tcp-upload-open/
http://www.candelatech.com/examples/cap-ath10k-tcp-upload-wpa2/

Some notes are near the top of each report, and in general:

The station machine is sending to/from wired Eth1 to/from the
stations, ie it is both sides of the network.
The AP is configured as router.  Both systems are running
our customized 10.1.467-ct firmware, and near the latest ath10k kernel.  Station
machine is Fedora 17, AP is Fedora 19.  Both are 64-bit, CPU is a mobile core-i7,
8GB RAM, SSD hard drives (not that it should matter).

Due to the vagaries of ath10k hardware and our firmware, we get hardware acceleration when
sending encrypted packets, but we have to decrypt received packets on the CPU.

I am not sure why open TCP throughput is so bad compared to upload.
I'll run some UDP tests when I get a chance.


Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Here are some ath10k performance graphs.
Date: Sun, 30 Mar 2014 23:27:48 -0700	[thread overview]
Message-ID: <53390AE4.4030705@candelatech.com> (raw)

I finally have a firmware stable enough to do some throughput
tests (only locked station machine up once doing these!).

I find the download test interesting where the rx link rate goes very low
after 12 or so stations.

tx link rate is not reported properly yet by ath10k, so ignore that.

http://www.candelatech.com/examples/cap-ath10k-tcp-download-open/
http://www.candelatech.com/examples/cap-ath10k-tcp-download-wpa2/
http://www.candelatech.com/examples/cap-ath10k-tcp-upload-open/
http://www.candelatech.com/examples/cap-ath10k-tcp-upload-wpa2/

Some notes are near the top of each report, and in general:

The station machine is sending to/from wired Eth1 to/from the
stations, ie it is both sides of the network.
The AP is configured as router.  Both systems are running
our customized 10.1.467-ct firmware, and near the latest ath10k kernel.  Station
machine is Fedora 17, AP is Fedora 19.  Both are 64-bit, CPU is a mobile core-i7,
8GB RAM, SSD hard drives (not that it should matter).

Due to the vagaries of ath10k hardware and our firmware, we get hardware acceleration when
sending encrypted packets, but we have to decrypt received packets on the CPU.

I am not sure why open TCP throughput is so bad compared to upload.
I'll run some UDP tests when I get a chance.


Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2014-03-31  6:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  6:27 Ben Greear [this message]
2014-03-31  6:27 ` Here are some ath10k performance graphs Ben Greear
2014-03-31 15:47 ` Ben Greear
2014-03-31 15:47   ` Ben Greear

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=53390AE4.4030705@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@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.