From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <m.sujith@gmail.com>
Cc: linux-wireless@vger.kernel.org, jouni.malinen@atheros.com
Subject: Re: [RFC v2] mac80211: Add 802.11h CSA support
Date: Tue, 30 Dec 2008 11:45:49 +0100 [thread overview]
Message-ID: <1230633949.3850.11.camel@johannes> (raw)
In-Reply-To: <18777.64102.60878.194252@localhost.localdomain> (sfid-20081230_114208_708501_346345E9)
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Tue, 2008-12-30 at 16:09 +0530, Sujith wrote:
> Johannes Berg wrote:
> > We already have a bss pointer here, would it be better to pass that in,
> > avoid the bss lookup, and do the bss lookup manually in the action frame
> > case, to avoid a double lookup here?
> >
>
> We don't have a bss pointer in ieee80211_rx_h_action(), where CSA
> action frames are handled too.
Yeah I know, I'm just wondering if it's worth saving the lookup in the
other case by doing the lookup outside of ieee80211_process_chanswitch()
and in ieee80211_rx_h_action()
> > Didn't you want to put this into the workqueue?
>
> Calling ieee80211_hw_config() from the timer was problematic since
> drivers might use a mutex, this won't matter.
> But if it makes things clearer, I can add it to the workqueue here too.
But the RX stuff (rx_h_action) is from a tasklet or directly from the
driver, and in the tasklet we can't sleep either, and if we call back
from ieee80211_rx() into rx_h_action into the driver again via config()
the driver might not like it? Or am I totally off base right now?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-12-30 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 10:26 [RFC v2] mac80211: Add 802.11h CSA support Sujith
2008-12-30 10:35 ` Johannes Berg
2008-12-30 10:39 ` Sujith
2008-12-30 10:45 ` Johannes Berg [this message]
2008-12-30 10:51 ` Sujith
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=1230633949.3850.11.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=jouni.malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox