From: Johannes Berg <johannes@sipsolutions.net>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC v2] mac80211: no BSS changes to driver from beacons processed during scanning
Date: Tue, 29 Apr 2008 17:26:47 +0200 [thread overview]
Message-ID: <1209482807.3960.42.camel@johannes.berg> (raw)
In-Reply-To: <1207785375-13470-1-git-send-email-reinette.chatre@intel.com>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Wed, 2008-04-09 at 16:56 -0700, Reinette Chatre wrote:
> There is no need to send BSS changes to driver from beacons processed
> during scanning. We are more interested in beacons from an AP with which
> we are associated - these will still be used to send updates to driver as
> the beacons are received without scanning.
>
> This change·removes the requirement that bss_info_changed needs to be atomic.
> The beacons received during scanning are processed from a tasklet, but if we
> do not call bss_info_changed for these beacons there is no need for it to be
> atomic. This function (bss_info_changed) is called either from workqueue or
> ioctl in all other instances.
Should we do the same for conf_tx, i.e. ieee80211_sta_wmm_params? I'm
not entirely sure the IBSS code doesn't still call it in a non-blocking
context though.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-04-30 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 23:56 [PATCH RFC v2] mac80211: no BSS changes to driver from beacons processed during scanning Reinette Chatre
2008-04-11 21:11 ` Johannes Berg
2008-04-29 15:26 ` Johannes Berg [this message]
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=1209482807.3960.42.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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