From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] mac80211: move csa counters from sdata to beacon/presp
Date: Thu, 22 May 2014 15:43:15 +0200 [thread overview]
Message-ID: <1400766195.4174.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1400765294-14732-2-git-send-email-michal.kazior@tieto.com> (sfid-20140522_153529_435766_85FBB99B)
On Thu, 2014-05-22 at 15:28 +0200, Michal Kazior wrote:
> Having csa counters part of beacon and probe_resp
> structures makes it easier to get rid of possible
> reaces between setting a beacon and updating
> counters on SMP systems by guaranteeing counters
> are always consistent against given beacon struct.
This makes a lot of sense.
> static int ieee80211_assign_beacon(struct ieee80211_sub_if_data *sdata,
> - struct cfg80211_beacon_data *params)
> + struct cfg80211_beacon_data *params,
> + const u16 *csa_counter_offset_beacon,
> + int n_csa_counter_offset_beacon,
> + const u16 *csa_counter_offset_presp,
> + int n_csa_counter_offset_presp,
> + u8 csa_count)
But that seems overkill. Maybe those CSA-related arguments could be in
some new struct so you don't have to pass "..., NULL, 0, NULL, 0, 0"?
johannes
next prev parent reply other threads:[~2014-05-22 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 13:28 [PATCH 0/3] mac80211: fix csa counters Michal Kazior
2014-05-22 13:28 ` [PATCH 1/3] mac80211: move csa counters from sdata to beacon/presp Michal Kazior
2014-05-22 13:43 ` Johannes Berg [this message]
2014-05-22 13:53 ` Michal Kazior
2014-05-22 14:37 ` Johannes Berg
2014-05-22 14:38 ` Johannes Berg
2014-05-22 13:28 ` [PATCH 2/3] mac80211: use csa counter offsets instead of csa_active Michal Kazior
2014-05-22 13:45 ` Johannes Berg
2014-05-22 13:59 ` Michal Kazior
2014-05-22 14:38 ` Johannes Berg
2014-05-22 13:28 ` [PATCH 3/3] mac80211: make csa_currnet_counter atomic Michal Kazior
2014-05-22 13:50 ` Johannes Berg
2014-05-22 14:03 ` Michal Kazior
2014-05-22 14:36 ` 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=1400766195.4174.13.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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