From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: A-MSDU Size & A-MPDU TX
Date: Thu, 06 Jan 2011 10:36:48 -0800 [thread overview]
Message-ID: <4D260BC0.8060600@candelatech.com> (raw)
In-Reply-To: <19D659FE-DFC3-4A9F-9A2C-1529E54294B5@zinkconsulting.com>
On 01/06/2011 10:21 AM, Galen wrote:
> What determines the maximum A-MSDU size for a given ath9k radio?
>
> For example, most (or all?) of my ath9k radios (AR5008, AR9280) seem to report an A-MSDU limit of 3839 bytes. However, the 802.11n specification allows up to 7935 bytes. Is this a true hardware limitation? Does it apply to all ath9k hardware? (Including AR9003/AR9380)
>
> Also, it appears that A-MPDU is entirely unsupported, at least for transmit purposes. It appears to be supported for receive purposes, but several posts say this is untested.
It seems to be used on my NICs (based on xmit counters in debugfs).
What makes you think it isn't working?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-01-06 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 18:21 [ath9k-devel] ath9k: A-MSDU Size & A-MPDU TX Galen
2011-01-06 18:36 ` Ben Greear [this message]
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=4D260BC0.8060600@candelatech.com \
--to=greearb@candelatech.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.