From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
nbd@openwrt.org, sujith@msujith.org,
Andrei Otcheretianski <andrei.otcheretianski@intel.com>
Subject: Re: [PATCH 2/3] ath9k: make rxfilter per HW
Date: Mon, 22 Jun 2015 13:59:40 +0200 [thread overview]
Message-ID: <1434974380.19597.10.camel@sipsolutions.net> (raw)
In-Reply-To: <1434974312.19597.9.camel@sipsolutions.net> (sfid-20150622_135841_850054_31462557)
On Mon, 2015-06-22 at 13:58 +0200, Johannes Berg wrote:
> On Mon, 2015-06-22 at 13:43 +0200, Janusz Dziedzic wrote:
> > mac80211 configure rxfilter per HW,
> > so we don't need this per channel.
>
> As I said before, I think there's value in mac80211 doing it per chanctx
> or even per vif, and it should be more efficient to do so.
>
> It's tempting to do it per vif and leave the chanctx work up to the
> driver, but perhaps with CSA and all that it gets complicated enough
> that doing it per chanctx in mac80211 would make sense?
On the other hand, I think our device requires it per vif, so we'd
probably have to do both.
+Andrei, who was looking into this.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
next prev parent reply other threads:[~2015-06-22 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 11:43 [PATCH 0/3] ath9k: P2P patches when chanctx used Janusz Dziedzic
2015-06-22 11:43 ` [PATCH 1/3] ath9k: handle RoC abort correctly Janusz Dziedzic
2015-06-22 11:56 ` Krishna Chaitanya
2015-06-22 13:02 ` Michal Kazior
2015-06-22 14:01 ` Krishna Chaitanya
2015-06-23 7:28 ` Janusz Dziedzic
2015-06-22 11:43 ` [PATCH 2/3] ath9k: make rxfilter per HW Janusz Dziedzic
2015-06-22 11:58 ` Johannes Berg
2015-06-22 11:59 ` Johannes Berg [this message]
2015-06-22 17:58 ` Felix Fietkau
2015-06-23 6:40 ` Otcheretianski, Andrei
2015-06-22 11:43 ` [PATCH 3/3] ath9k: advertise p2p dev support when chanctx Janusz Dziedzic
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=1434974380.19597.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrei.otcheretianski@intel.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=sujith@msujith.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).