From: Johannes Berg <johannes@sipsolutions.net>
To: mpubbise@qti.qualcomm.com
Cc: linux-wireless@vger.kernel.org,
Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Subject: Re: [RFCv2 1/2] mac80211: Add provision for 802.11 encap offload
Date: Fri, 03 Mar 2017 13:29:18 +0100 [thread overview]
Message-ID: <1488544158.25750.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1488540807-27415-2-git-send-email-mpubbise@qti.qualcomm.com>
On Fri, 2017-03-03 at 17:03 +0530, mpubbise@qti.qualcomm.com wrote:
> From: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
>
> Drivers can have the capability to offload 802.11 encap
> to firmware or hardware for data frames. This patch adds a new
> hw_flag for driver to advertise the offload support.
> Transmit path offloading 802.11 header (including cipher headers)
> encap for data frames will be implemented in a separate patch.
>
> Drivers advertising this capability should also implement other
> functionalities which deal with 802.11 frame format like below
>
> - Hardware encryption
> - Aggregation of A-MSDU offload
> - Fragmentation offload
Not much point in having this as a separate patch, but this
documentation paragraph should move into the documentation for the new
flag in mac80211.h
johannes
next prev parent reply other threads:[~2017-03-03 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 11:33 [RFCv2 0/2] Add new transmit data path for ethernet frame format mpubbise
2017-03-03 11:33 ` [RFCv2 1/2] mac80211: Add provision for 802.11 encap offload mpubbise
2017-03-03 12:29 ` Johannes Berg [this message]
2017-03-08 15:49 ` Pubbisetty, Manikanta
2017-03-03 11:33 ` [RFCv2 2/2] mac80211: Implement data xmit " mpubbise
2017-03-03 12:39 ` Johannes Berg
2017-03-08 15:46 ` Pubbisetty, Manikanta
2017-03-08 21:33 ` Johannes Berg
2017-03-09 9:56 ` Pubbisetty, Manikanta
2017-03-14 14:11 ` Johannes Berg
2017-03-21 5:36 ` Manikanta Pubbisetty
2017-03-31 11:52 ` Johannes Berg
2017-04-11 6:06 ` Manikanta Pubbisetty
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=1488544158.25750.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@qti.qualcomm.com \
--cc=vthiagar@qti.qualcomm.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 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.