linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: linux-wireless@vger.kernel.org, benjamin@sipsolutions.net
Subject: Re: [PATCH 5/7] mac80211: add wide bandwidth channel switch announcement to CSA action frames and mesh beacons
Date: Fri, 19 May 2017 13:33:37 +0200	[thread overview]
Message-ID: <1495193617.3274.7.camel@sipsolutions.net> (raw)
In-Reply-To: <20170516092316.15636-6-sw@simonwunderlich.de> (sfid-20170516_112329_694356_1BF36491)

I've applied patches 1-4 now.

The subject is a bit long - I was going to change it to

    mac80211: mesh: support sending wide bandwidth CSA
    
    To support HT and VHT channel switch announcements, both beacons
    and action frames must include the corresponding IEs.

but:

> +		   2 + 2 + sizeof(struct
> ieee80211_wide_bw_chansw_ie) +
> +		   2 + sizeof(struct ieee80211_sec_chan_offs_ie) +

The "2 + 2" should have a comment - no that I'm even really sure that
you need the wrapper?

> -		pos = skb_put(skb, 13);
> -		memset(pos, 0, 13);

Removing that is nice - but why do you do this:

> +		bool have_secondary_chan_offset = false;
> +		bool have_wide_bandwidth_cs = false;
> +		int ie_len = 2 + sizeof(struct
> ieee80211_channel_sw_ie) +
> +			     2 + sizeof(struct
> ieee80211_mesh_chansw_params_ie);
> +
> +		switch (csa->settings.chandef.width) {
> +		case NL80211_CHAN_WIDTH_80:
> +		case NL80211_CHAN_WIDTH_80P80:
> +		case NL80211_CHAN_WIDTH_160:
> +			have_wide_bandwidth_cs = true;
> +			ie_len += 2 + 2 +
> +				  sizeof(struct
> ieee80211_wide_bw_chansw_ie);
> +			break;
> +		case NL80211_CHAN_WIDTH_40:
> +			have_secondary_chan_offset = true;
> +			ie_len += 2 + sizeof(struct
> ieee80211_sec_chan_offs_ie);
> +		default:
> +			break;
> +		}
> +		pos = skb_put(skb, ie_len);
> +		memset(pos, 0, ie_len);

I think having multiple calls to skb_put() would be better.

>  		*pos++ = WLAN_EID_CHANNEL_SWITCH;
>  		*pos++ = 3;
>  		*pos++ = 0x0;
> @@ -760,6 +781,28 @@ ieee80211_mesh_build_beacon(struct
> ieee80211_if_mesh *ifmsh)
>  		pos += 2;
>  		put_unaligned_le16(ifmsh->pre_value, pos);
>  		pos += 2;
> +
> +		if (have_secondary_chan_offset) {
> +			enum nl80211_channel_type ct;

You can have one here, and re-initialize pos.

> +			*pos++ = WLAN_EID_SECONDARY_CHANNEL_OFFSET;
> /* EID */
> +			*pos++ = 1;				 
>    /* len */
> +			ct = cfg80211_get_chandef_type(&csa-
> >settings.chandef);
> +			if (ct == NL80211_CHAN_HT40PLUS)
> +				*pos++ =
> IEEE80211_HT_PARAM_CHA_SEC_ABOVE;
> +			else
> +				*pos++ =
> IEEE80211_HT_PARAM_CHA_SEC_BELOW;
> +		}
> +
> +		if (have_wide_bandwidth_cs) {
> +			struct cfg80211_chan_def *chandef;

and likewise here.

That'd also be safer in a way.

johannes

  reply	other threads:[~2017-05-19 11:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16  9:23 [PATCH 0/7] extend mac80211 mesh DFS and CSA functionality Simon Wunderlich
2017-05-16  9:23 ` [PATCH 1/7] mac80211: Mark channel as unusable if a regulatory MESH CSA is received Simon Wunderlich
2017-05-16  9:23 ` [PATCH 2/7] wireless: Only join DFS channels in mesh mode if userspace flags support Simon Wunderlich
2017-05-16  9:23 ` [PATCH 3/7] wireless: Require HANDLE_DFS flag to switch channel for non-AP mode Simon Wunderlich
2017-05-16  9:23 ` [PATCH 4/7] mac80211: Allow following CSA to DFS channels if userspace handles it Simon Wunderlich
2017-05-16  9:23 ` [PATCH 5/7] mac80211: add wide bandwidth channel switch announcement to CSA action frames and mesh beacons Simon Wunderlich
2017-05-19 11:33   ` Johannes Berg [this message]
2017-05-19 11:45     ` Simon Wunderlich
2017-05-19 11:51       ` Johannes Berg
2017-05-16  9:23 ` [PATCH 6/7] mac80211: enable VHT for mesh channel processing Simon Wunderlich
2017-05-16  9:23 ` [PATCH 7/7] mac80211: mark as action frame when parsing IEs of CSA action frames Simon Wunderlich
2017-05-19 11:35   ` Johannes Berg
2017-05-16  9:44 ` [PATCH 0/7] extend mac80211 mesh DFS and CSA functionality Bastian Bittorf
2017-05-16 10:18   ` Simon Wunderlich
2017-05-16 11:55     ` Bastian Bittorf
2017-05-16 12:04       ` Simon Wunderlich

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=1495193617.3274.7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=benjamin@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sw@simonwunderlich.de \
    /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).