linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Porsch <marco@cozybit.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: devel@lists.open80211s.org, vthiagar@qca.qualcomm.com,
	jouni@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	mcgrof@qca.qualcomm.com, ath9k-devel@lists.ath9k.org,
	senthilb@qca.qualcomm.com, johannes@sipsolutions.net
Subject: Re: [PATCH 1/3] mac80211: move mesh sync beacon handler into neighbour_update
Date: Fri, 15 Feb 2013 14:30:21 +0100	[thread overview]
Message-ID: <511E386D.1010806@cozybit.com> (raw)
In-Reply-To: <20130215124255.GB3493@localhost>

Hi,

On 02/15/2013 01:42 PM, Bob Copeland wrote:
> On Fri, Feb 15, 2013 at 07:40:46AM -0500, Bob Copeland wrote:
>>> I don't think you should drop this comment; also why not just address
>>> it? There's a timestamp in rx_status that should be the correct one for
>>> ath9k (which is pretty much all this seems to work on anyway :) )
>>
>> The comment is just moved?  Mesh already uses rx_status->mactime, if
>> the driver supplies it, which the comment says :)
>
> Oh I see - you are saying not to drop the comment about rcu locking.

 > diff --git a/net/mac80211/mesh_plink.c b/net/mac80211/mesh_plink.c
 > index f7526e5..fe6fc22 100644
 > --- a/net/mac80211/mesh_plink.c
 > +++ b/net/mac80211/mesh_plink.c
 > @@ -488,13 +489,19 @@ mesh_sta_info_get(struct ieee80211_sub_if_data 
*sdata,
 >    * Initiates peering if appropriate.
 >    */
 >   void mesh_neighbour_update(struct ieee80211_sub_if_data *sdata,
 > -			   u8 *hw_addr,
 > -			   struct ieee802_11_elems *elems)
 > +			   struct ieee80211_mgmt *mgmt,
 > +			   struct ieee802_11_elems *elems,
 > +			   struct ieee80211_rx_status *rx_status)
 >   {
 > +	struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh;
 >   	struct sta_info *sta;
 >   	u32 changed = 0;
 > +	u64 tsf;
 >
 > -	sta = mesh_sta_info_get(sdata, hw_addr, elems);
 > +	/* get tsf before entering rcu-read section */

The comment about RCU lock moved here.

 > +	tsf = drv_get_tsf(sdata->local, sdata);
 > +
 > +	sta = mesh_sta_info_get(sdata, mgmt->sa, elems);
 >   	if (!sta)
 >   		goto out;
 >

--Marco

  reply	other threads:[~2013-02-15 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 11:40 [PATCH 1/3] mac80211: move mesh sync beacon handler into neighbour_update Marco Porsch
2013-02-15 11:40 ` [PATCH 2/3] mac80211: mesh power save doze scheduling Marco Porsch
2013-02-15 11:40 ` [PATCH 3/3] ath9k: mesh powersave support Marco Porsch
2013-02-15 12:14 ` [PATCH 1/3] mac80211: move mesh sync beacon handler into neighbour_update Johannes Berg
2013-02-15 12:40   ` Bob Copeland
2013-02-15 12:42     ` Bob Copeland
2013-02-15 13:30       ` Marco Porsch [this message]
2013-02-15 12:40   ` marco
2013-02-15 12:46     ` Johannes Berg
2013-02-15 13:31       ` Marco Porsch
2013-02-15 13:37         ` Johannes Berg
2013-02-15 13:48           ` Marco Porsch
2013-02-15 13:58             ` Johannes Berg
2013-02-18 15:07               ` Marco Porsch
2013-02-18 15:20                 ` 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=511E386D.1010806@cozybit.com \
    --to=marco@cozybit.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=devel@lists.open80211s.org \
    --cc=johannes@sipsolutions.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@qca.qualcomm.com \
    --cc=me@bobcopeland.com \
    --cc=senthilb@qca.qualcomm.com \
    --cc=vthiagar@qca.qualcomm.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).