From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <m.sujith@gmail.com>
Cc: linux-wireless@vger.kernel.org, mcgrof@gmail.com,
jouni.malinen@atheros.com
Subject: Re: [RFC] Handle Channel Switch Announcement
Date: Wed, 17 Dec 2008 19:07:52 +0100 [thread overview]
Message-ID: <1229537272.4268.7.camel@localhost> (raw)
In-Reply-To: <18761.4838.509784.281821@localhost.localdomain> (sfid-20081217_155745_335359_22B180E6)
On Wed, 2008-12-17 at 20:25 +0530, Sujith wrote:
> + * @IEEE80211_CHAN_CSA_DISABLED: Disabled because a
> + Channel Switch Announcement was received on this channel.
I agree with Jouni, this is probably not a good idea, especially since
this flag would be shared between hardware for those drivers that have
the channel structs allocated statically. We should probably just stick
a struct ieee80211_channel *switch_from; pointer somewhere into the
sdata struct or so.
> --- a/net/mac80211/rx.c
> +++ b/net/mac80211/rx.c
> @@ -1612,6 +1612,13 @@ ieee80211_rx_h_action(struct ieee80211_rx_data *rx)
> return RX_DROP_MONITOR;
> ieee80211_process_measurement_req(sdata, mgmt, len);
> break;
> + case WLAN_ACTION_SPCT_CHL_SWITCH:
> + if (len < (IEEE80211_MIN_ACTION_SIZE +
> + sizeof(mgmt->u.action.u.chan_switch)))
> + return RX_DROP_MONITOR;
> + ieee80211_process_chanswitch(sdata,
> + &mgmt->u.action.u.chan_switch.sw_elem);
I think I'd like to have them dropped to monitor for !station here,
instead of silently in the processing function.
> +
> +void ieee80211_chswitch_timer(unsigned long data)
> +{
> + struct ieee80211_bss *bss;
> + struct ieee80211_sub_if_data *sdata =
> + (struct ieee80211_sub_if_data *) data;
> + struct ieee80211_if_sta *ifsta = &sdata->u.sta;
> +
> + printk("expire\n");
That should probably be removed or be more specific & protected by some
debug #ifdef.
> +void ieee80211_process_chanswitch(struct ieee80211_sub_if_data *sdata,
> + struct ieee80211_channel_sw_ie *sw_elem)
> + } else {
> + ieee80211_stop_queues(&sdata->local->hw);
Can you rebase this on top of Kalle's patch that adds the "stop reasons"
for each queue? As it is now, the driver could wake up the queues again
if one was full.
johannes
next prev parent reply other threads:[~2008-12-17 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 14:55 [RFC] Handle Channel Switch Announcement Sujith
2008-12-17 16:20 ` Jouni Malinen
2008-12-18 1:32 ` Sujith
2008-12-18 3:59 ` Sujith
2008-12-18 7:05 ` Jouni Malinen
2008-12-18 7:18 ` Jouni Malinen
2008-12-17 18:07 ` Johannes Berg [this message]
2008-12-18 1:36 ` 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=1229537272.4268.7.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=jouni.malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@gmail.com \
--cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).