From: Kalle Valo <kvalo@codeaurora.org>
To: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: add dynamic vlan support
Date: Tue, 24 Apr 2018 11:09:13 +0300 [thread overview]
Message-ID: <87r2n5auvq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1524232653-22573-1-git-send-email-mpubbise@codeaurora.org> (Manikanta Pubbisetty's message of "Fri, 20 Apr 2018 19:27:33 +0530")
Manikanta Pubbisetty <mpubbise@codeaurora.org> writes:
> Mutlicast/broadcast traffic destined for a particular vlan group will
> always be encrypted in software. To enable dynamic VLANs, it requires
> driver support for sending software encrypted packets.
>
> In ath10k, sending sw encrypted frames is allowed only when we insmod
> the driver with cryptmode param set to 1, this configuration disables
> hardware crypto and enables RAW mode implicitly. Since, enabling raw
> mode has performance impact, this cannot be considered as an ideal
> solution for supporting VLANs in the driver.
>
> As an alternative take, in this approach, cryptographic keys for
> unicast traffic(per peer PTKs) and keys for non-vlan group traffic
> will be configured in hardware, allowing hardware encryption for unicast
> and non-vlan group traffic. Only vlan group traffic will be encrypted in
> software and pushed to the target with encap mode set to RAW in the TX
> descriptors.
>
> Not all firmwares can support this type of key configuration(having few
> keys installed in hardware and few only in software); for this purpose a
> new WMI service flag "WMI_SERVICE_PER_PACKET_SW_ENCRYPT" is introduced to
> advertise this support.
>
> Also, adding the logic required to send sw encrypted frames in raw mode.
>
> Tested this change on QCA9984(firmware version 10.4-3.5.3-00057).
>
> Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Your name in patchwork is wrong and hence my script uses the wrong
name. Please fix it by registering to patchwork[1] where it's possible
to change your name during registration, but only one time. If that
doesn't work then send a request to helpdesk@kernel.org and the admins
can fix it.
[1] https://patchwork.kernel.org/register/
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-24 8:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 13:57 [PATCH] ath10k: add dynamic vlan support Manikanta Pubbisetty
2018-04-23 19:18 ` Sebastian Gottschall
2018-05-18 9:53 ` Johannes Berg
2018-05-18 10:40 ` Sebastian Gottschall
2018-04-24 8:09 ` Kalle Valo [this message]
2018-04-24 9:09 ` Sebastian Gottschall
2018-04-24 9:18 ` Manikanta Pubbisetty
2018-04-24 9:52 ` Kalle Valo
2018-04-24 9:55 ` Sebastian Gottschall
2018-05-04 6:50 ` Manikanta Pubbisetty
2018-05-05 9:50 ` Sebastian Gottschall
2018-05-18 9:54 ` Johannes Berg
2018-05-18 10:52 ` Sebastian Gottschall
2018-05-21 6:42 ` Manikanta Pubbisetty
2018-05-23 9:50 ` Johannes Berg
2018-05-23 10:39 ` Manikanta Pubbisetty
2018-05-23 10:39 ` Johannes Berg
2018-05-23 10:50 ` Manikanta Pubbisetty
2018-05-24 4:41 ` Sebastian Gottschall
2018-06-18 20:49 ` Johannes Berg
2018-08-14 12:53 ` Manikanta Pubbisetty
2018-08-16 8:27 ` Johannes Berg
2018-08-24 5:50 ` Manikanta Pubbisetty
2018-09-03 10:39 ` Johannes Berg
2018-09-05 6:03 ` Manikanta Pubbisetty
[not found] ` <15ca06c2-0d43-99c1-8f31-19e73629ab70@codeaurora.org>
2018-08-24 8:14 ` Kalle Valo
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=87r2n5auvq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@codeaurora.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