linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 14:10:06 +0530	[thread overview]
Message-ID: <20110415084005.GC11576@hertz.marvell.com> (raw)
In-Reply-To: <1302850527.3572.2.camel@jlt3.sipsolutions.net>

On Thu, Apr 14, 2011 at 11:55:27PM -0700, Johannes Berg wrote:
> On Fri, 2011-04-15 at 10:23 +0530, Yogesh Ashok Powar wrote:
> > When drivers use HW crypto, reservation for tail room is not needed for
> > any crypto suite. Do not reserve tail room in such cases, this helps in
> > optimizing the transmit path.
> > 
> > Signed-off-by: Yogesh Ashok Powar <yogeshp@marvell.com>
> 
> NACK.
> 
> >  	/*
> > -	 * This could be optimised, devices that do full hardware
> > -	 * crypto (including TKIP MMIC) need no tailroom... But we
> > -	 * have no drivers for such devices currently.
> > +	 * When full HW crypto is being used by the driver,
> > +	 * no tail room is needed. Hence do not ask for tail room
> > +	 * in such cases. This will avoid copying the skb in
> > +	 * pskb_expand_head.
> >  	 */
> > -	if (may_encrypt) {
> > +	if (!(local->hw.flags & IEEE80211_HW_CRYPTO_ENABLED) && may_encrypt) {
> 
> There's no need for this as a HW flag, and in its present form it is
> EXTREMELY likely to be misused completely. And realise that even drivers
> that implement HW crypto may need the extra tailroom for TKIP MMIC, so
> your description of the flag is completely bogus.
> 
> You can implement the performance feature, but only by keeping track of
> which keys need tailroom and skipping the code here once they are all
> programmed into the device which will handle them including MMIC.

Thanks for the information. 

Just for my understanding before I attempt patch set V2, please let me
know if the approach given below makes sense.

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. 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).

Thanks
Yogesh 
> 
> johannes
> 

  reply	other threads:[~2011-04-15  8:48 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 [this message]
2011-04-15  8:52     ` Johannes Berg
2011-04-15 10:51       ` Yogesh Ashok Powar
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=20110415084005.GC11576@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).