From: Yogesh Ashok Powar <yogeshp@marvell.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [PATCH 1/2] mac80211: Adding HW flag IEEE80211_HW_CRYPTO_ENABLED
Date: Fri, 15 Apr 2011 16:21:44 +0530 [thread overview]
Message-ID: <20110415105140.GD11576@hertz.marvell.com> (raw)
In-Reply-To: <1302857554.3572.14.camel@jlt3.sipsolutions.net>
On Fri, Apr 15, 2011 at 01:52:34AM -0700, Johannes Berg wrote:
> On Fri, 2011-04-15 at 14:10 +0530, Yogesh Ashok Powar wrote:
>
> > Define a flag say IEEE80211_CRYPTO_NO_TAILROOM_NEEDED per key. Drivers
> > need to set this flag in set_key handler for the keys which requires no
> > extra tailroom.
>
> This isn't necessary. You already know from the existing flags, the only
> relevant one is IEEE80211_KEY_FLAG_GENERATE_MMIC which must be unset.
Ok. We will use this flag.
>
> > Then Skip the code which expands the skb iff
> > IEEE80211_CRYPTO_NO_TAILROOM_NEEDED is set and the key is programmed
> > into the hardware (checking KEY_FLAG_UPLOADED_TO_HARDWARE).
>
> You don't know the key at this point, so you have to keep track of
> whether this is true for all keys, which depends on whether or not
> they're already programmed into the HW (since for SW crypto we need the
> tailroom)
>From this it seems that we do not reserve tailroom iff
IEEE80211_KEY_FLAG_GENERATE_MMIC flag is unset for all keys and all the keys
are programmed into the hardware.
Also, say in mixed mode if TKIP and CCMP keys are configured and this
flag is set for TKIP MMIC, we will end up reserving tailroom even for
CCMP. Is my understanding correct?
Also, though I have not looked into this part of the code very closely,
how about deriving key information at this place? Will that be feasible?
Thanks
Yogesh
next prev parent reply other threads:[~2011-04-15 10:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 4:53 [PATCH 1/2] mac80211: Adding HW flag IEEE80211_HW_CRYPTO_ENABLED Yogesh Ashok Powar
2011-04-15 6:55 ` Johannes Berg
2011-04-15 8:40 ` Yogesh Ashok Powar
2011-04-15 8:52 ` Johannes Berg
2011-04-15 10:51 ` Yogesh Ashok Powar [this message]
2011-04-15 11:01 ` Johannes Berg
2011-04-21 12:15 ` Yogesh Ashok Powar
2011-04-21 12:33 ` Johannes Berg
2011-04-21 12:38 ` Johannes Berg
2011-04-21 12:46 ` Yogesh Ashok Powar
2011-04-21 12:59 ` Johannes Berg
2011-04-27 11:03 ` Yogesh Ashok Powar
2011-04-27 11:27 ` Johannes Berg
2011-04-27 11:40 ` Yogesh Ashok Powar
2011-04-27 11:53 ` Johannes Berg
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=20110415105140.GD11576@hertz.marvell.com \
--to=yogeshp@marvell.com \
--cc=buytenh@wantstofly.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 NNTP newsgroup(s).