From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Question on keycache size.
Date: Thu, 12 Jan 2012 15:59:15 -0800 [thread overview]
Message-ID: <4F0F73D3.9010805@candelatech.com> (raw)
In-Reply-To: <CAJ-Vmokxe7Ltdf664hRSTh+OVq-XXGwAizX5h05k2oWEPOKydw@mail.gmail.com>
On 01/12/2012 03:53 PM, Adrian Chadd wrote:
> Let me go and hit up the MAC guys and find exactly what the heck is
> being kept in the keycache. There may be some good reasons it's being
> done that I'm not yet aware of.
>
> At least the (legacy, but not sure for Kite/similar) fast diversity
> stuff is kept in the keycache? As well as the filtered frame bits.
There is lots being kept there, but the code appears to deal with
invalid key caches just fine (and this appears to be the expected
code path when nohwcrypt is enabled.)
You can see what it pokes into the chip in the ath/key.c file.
Grepping for ath_key in the ath/ath9k/ dir shows the calling
code..and so forth.
Eventually the rx and tx logic has checks for
keyix == ATH9K_RXKEYIX_INVALID, and appears to deal with
things OK if that is the case.
I still look forward to hearing about anything you learn on
this topic, however!
Thanks,
Ben
>
>
> Adrian
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-01-12 23:59 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
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 [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=4F0F73D3.9010805@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.