From: Mahesh Kumar <mkumar@solectek.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Atheros Throughput with Aggregation & Encryption
Date: Mon, 28 Jul 2008 17:33:03 -0700 [thread overview]
Message-ID: <488E653F.5060008@solectek.com> (raw)
In-Reply-To: <1490851897-1217291691-cardhu_decombobulator_blackberry.rim.net-512143513-@bxe135.bisx.prod.on.blackberry>
We are using the latest driver.
Kernel version is 2.6.13
armeb-linux-uclibc-gcc version 3.4.3, for xscale
charles at thewybles.com wrote:
> What version of the code?
> What version of the linux kernel?
> What compile tool chain?
> What distro?
>
> Thanks.
>
> Charles
>
>
> ------Original Message------
> From: Mahesh Kumar
> Sender: ath9k-devel-bounces at lists.ath9k.org
> To: ath9k-devel at lists.ath9k.org
> ReplyTo: mkumar at solectek.com
> Sent: Jul 28, 2008 4:11 PM
> Subject: [ath9k-devel] Atheros Throughput with Aggregation & Encryption
>
> Hello,
>
> We have a critical issue in getting the high throughput, once we enable
> both the Aggregation (AMPDU) and Encryption (WPA) at the same time. (We
> are using the AR9160 chipset.)
>
> Our test setup is like this,
>
> [PC1] ---> [Access Point] --> [Client] --> [PC2].
>
> We are sending a 100 Mbps of UDP traffic from PC1 to PC2. The
> Aggregation (AMPDU) & Encryption are enabled on both "Access point" and
> the "Client". Very low traffic ( < 1Mbps) is reaching@the PC2, that
> also occasionally. Most of the traffic is dropped at the Access point
> itself. When we check the transmit status descriptor at the Access
> point, it shows , lots of "Tx delimiter under-run error" & " Tx data
> under-run error".
>
> Once the driver gets "under-run" error, it starts adjusting the Tx FIFO
> trigger level [TXCFG register, Frame Trigger level], and it finally
> reaches it's maximum. This register specifies the minimum number of
> bytes that must be DMAed into the PCU TXFIFO, before the PCU initiates
> the frame on the air.
>
> Any idea on why it's happening ?. Are we missing any special kind of
> configuration ?. Or is there any known issue when we enable both
> Aggregation (AMPDU) and encryption simultaneously ?.
>
> The same setup is working, if we disable the Encryption ( getting around
> 95.7 Mbps). Also the encryption alone is working, without the
> Aggregation, though we are getting a degraded performance ( max around
> 30 Mbps.)
>
>
> Thanks in advance,
> Mahesh.
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
>
> Sent via BlackBerry from T-Mobile
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
next prev parent reply other threads:[~2008-07-29 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:33 [ath9k-devel] Atheros Throughput with Aggregation & Encryption charles at thewybles.com
2008-07-29 0:33 ` Mahesh Kumar [this message]
2008-07-29 3:10 ` Luis R. Rodriguez
2008-07-29 17:41 ` Mahesh Kumar
2008-07-29 20:17 ` Mahesh Kumar
2008-07-30 1:32 ` Sujith
-- strict thread matches above, loose matches on Subject: below --
2008-07-29 0:39 charles at thewybles.com
2008-07-29 0:38 ` Mahesh Kumar
2008-07-28 23:11 Mahesh Kumar
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=488E653F.5060008@solectek.com \
--to=mkumar@solectek.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 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.