From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@codeaurora.org>,
Karthikeyan Periyasamy <periyasa@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/2] ath10k: Add QCA vendor command/attr support to filterneighbor BSS frames
Date: Thu, 18 Oct 2018 10:29:32 +0200 [thread overview]
Message-ID: <a28348956ba3fbfded80bc78ba1c0335df7edb75.camel@sipsolutions.net> (raw)
In-Reply-To: <20181005060031.BA1EB60BF4@smtp.codeaurora.org>
On Fri, 2018-10-05 at 06:00 +0000, Kalle Valo wrote:
>
> So I'm not sure what to do with this. A bpf type of filtering system in
> mac80211 would be nice
Yes, I think we really need to start implementing that sooner rather
than later. I had something, must see if I can find time for it.
> but then again we cannot benefit from HW offloading.
Yes, that's a concern. But how big of a concern is it really?
This patch only talks about "allow an AP" etc. and so while important,
power isn't the _utmost_ concern like on mobile. Given an efficient
filtering solution in software, would that be sufficient?
johannes
next prev parent reply other threads:[~2018-10-18 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 11:51 [RFC 0/2] ath10k: Add QCA vendor command/attr support to filter neighbor BSS frames Karthikeyan Periyasamy
2018-07-05 11:51 ` [RFC 1/2] ath10k: add wmi interface for vdev_set_neighbor_rx_param Karthikeyan Periyasamy
2018-07-05 11:51 ` [RFC 2/2] ath10k: Add QCA vendor command/attr support to filter neighbor BSS frames Karthikeyan Periyasamy
2018-10-05 6:00 ` [RFC 2/2] ath10k: Add QCA vendor command/attr support to filterneighbor " Kalle Valo
[not found] ` <20181005060031.BA1EB60BF4@smtp.codeaurora.org>
2018-10-18 8:29 ` Johannes Berg [this message]
2018-11-20 2:40 ` Karthikeyan Periyasamy
2019-01-25 20:49 ` Johannes Berg
2019-01-28 4:49 ` Karthikeyan Periyasamy
2019-02-15 12:37 ` 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=a28348956ba3fbfded80bc78ba1c0335df7edb75.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=periyasa@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;
as well as URLs for NNTP newsgroup(s).