From: <mpubbise@qti.qualcomm.com>
To: <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>,
Manikanta Pubbisetty <mpubbise@qti.qualcomm.com>
Subject: [RFCv2 0/2] Add new transmit data path for ethernet frame format
Date: Fri, 3 Mar 2017 17:03:25 +0530 [thread overview]
Message-ID: <1488540807-27415-1-git-send-email-mpubbise@qti.qualcomm.com> (raw)
From: Manikanta Pubbisetty <mpubbise@qti.qualcomm.com>
This patch set adds a new transmit data path to offload 802.11 header
encap to driver/hardware. Drivers having support for ieee80211
header encap and other offload functionalities which can't be done
before encap can make use of this new data path. Currently it is
implemented for STA and AP interface type, this can be extend other
interface types like adhoc.
This patchset only adds support for tx in ethernet frame format
and receive can happen in 802.11 format with existing rx framework.
With ath10k driver changes using this new Tx/Rx path, 10 - 15%
CPU usage and upto ~20Mbps TCP performance improvements are
observed with this ethernet data path.
Vasanthakumar Thiagarajan (2):
mac80211: Add provision for 802.11 encap offload
mac80211: Implement data xmit for 802.11 encap offload
V2:
* 802.11 decap offload is removed from the patchset
* Code changes as per review comments of v1.
include/net/mac80211.h | 30 ++++++-
net/mac80211/cfg.c | 9 ++
net/mac80211/debugfs.c | 1 +
net/mac80211/ieee80211_i.h | 10 +++
net/mac80211/iface.c | 72 +++++++++++++++
net/mac80211/key.c | 3 +
net/mac80211/status.c | 79 +++++++++++++++++
net/mac80211/tx.c | 207 +++++++++++++++++++++++++++++++++++++++++++-
8 files changed, 406 insertions(+), 5 deletions(-)
--
1.7.9.5
next reply other threads:[~2017-03-03 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 11:33 mpubbise [this message]
2017-03-03 11:33 ` [RFCv2 1/2] mac80211: Add provision for 802.11 encap offload mpubbise
2017-03-03 12:29 ` Johannes Berg
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=1488540807-27415-1-git-send-email-mpubbise@qti.qualcomm.com \
--to=mpubbise@qti.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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).