From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Question on keycache size.
Date: Thu, 12 Jan 2012 12:14:03 -0800 [thread overview]
Message-ID: <4F0F3F0B.1010101@candelatech.com> (raw)
In-Reply-To: <CAJ-VmomRZ5CoJdXHG5ngb56tC_XHwm2Cackg36n8s=H-QrC3Aw@mail.gmail.com>
On 01/12/2012 11:46 AM, Adrian Chadd wrote:
> .. well, nohwcrypt still populates the keycache, just with no-crypt entries.
>
> I just wonder what other state is being kept in the keycache (eg
> filtered frame handling lives there IIRC, I don't recall where the
> aggregation state cache sits, but it shouldn't be required - it just
> means the bitmap would be "right" instead of "very right" (ie, keeping
> track of the previously-sent frames..))
>
> Ben: just verify that nohwcrypt still populates keycache entries?
Just starting to take a look. First thing I found is this in ath9k/init.c.
The comments make it seem like the limit is much lower than 128, but
perhaps that is only if hwcrypt is used...
/*
* Check whether the separate key cache entries
* are required to handle both tx+rx MIC keys.
* With split mic keys the number of stations is limited
* to 27 otherwise 59.
*/
if (sc->sc_ah->misc_mode & AR_PCU_MIC_NEW_LOC_ENA)
common->crypt_caps |= ATH_CRYPT_CAP_MIC_COMBINED;
Will continue digging.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-01-12 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 21:55 [ath9k-devel] Question on keycache size Ben Greear
2012-01-12 8:27 ` Mohammed Shafi
2012-01-12 16:02 ` Ben Greear
2012-01-12 19:46 ` Adrian Chadd
2012-01-12 20:14 ` Ben Greear [this message]
2012-01-12 20:34 ` Ben Greear
2012-01-12 23:11 ` Ben Greear
2012-01-12 23:53 ` Adrian Chadd
2012-01-12 23:59 ` 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=4F0F3F0B.1010101@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.