From: Le Tran Dat <trandatnh@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] What is the expected throughput of ath9k with 20Mhz channel bandwidth?
Date: Wed, 29 Jun 2016 11:01:22 +0000 [thread overview]
Message-ID: <CAOyZXpSJYkgKzH+v3jwzFOX8nRHJVuwsZZFJyi3q+RrBvXec0w@mail.gmail.com> (raw)
In-Reply-To: <CAOyZXpQWDLaU2As56fzVyxAJSzmmA6fW+f+4Nu1cNdj19Ts==w@mail.gmail.com>
Hi,
I am testing AR9342 Throughput with 20Mhz channel bandwidth, using
OpenWRT/LEDE firmware.
However, the throughput result is quite low. About 65Mbps to 70Mbps while
the bitrate is 144Mbps.
While testing I monitor the CPU usage and it's still free for about 30%.
Is it the best it can do? How to improve it?
Thanks,
Dat
--
Thanks,
Dat
Sending from my iPhone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160629/6eb8151c/attachment.htm
next prev parent reply other threads:[~2016-06-29 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 9:19 [ath9k-devel] What is the expected throughput of ath9k with 20Mhz channel bandwidth? Le Tran Dat
2016-06-29 11:01 ` Le Tran Dat [this message]
2016-06-29 11:23 ` Matthias May
2016-07-01 2:31 ` Le Tran Dat
2016-07-01 6:25 ` sandeep suresh
2016-07-01 7:29 ` Matthias May
2016-07-01 8:57 ` Le Tran Dat
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=CAOyZXpSJYkgKzH+v3jwzFOX8nRHJVuwsZZFJyi3q+RrBvXec0w@mail.gmail.com \
--to=trandatnh@gmail.com \
--cc=ath9k-devel@lists.ath9k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).