From: Johannes Berg <johannes@sipsolutions.net>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH v3] mac80211: Give it some time to do the TSF sync
Date: Mon, 23 Feb 2009 17:40:33 -0800 [thread overview]
Message-ID: <1235439633.4455.33.camel@johannes.local> (raw)
In-Reply-To: <20090221231800.227280@gmx.net> (sfid-20090222_001831_559891_2537405E)
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
On Sun, 2009-02-22 at 00:18 +0100, Alina Friedrichsen wrote:
> Give slow hardware some time to do the TSF sync, to not run into an
> IBSS merging endless loop in some rarely situations.
>
> Version 2 adds a comment.
>
> Version 3: I had forgotten to change the bracket.
>
> diff --git a/net/mac80211/ibss.c b/net/mac80211/ibss.c
> index 1bbfc70..ea737bf 100644
> --- a/net/mac80211/ibss.c
> +++ b/net/mac80211/ibss.c
> @@ -332,6 +332,10 @@ static void ieee80211_rx_bss_info(struct ieee80211_sub_if_data *sdata,
> jiffies);
> #endif
>
> + /* give slow hardware some time to do the TSF sync */
> + if (rx_timestamp < 0x400000)
> + goto put_bss;
Please elaborate on what this does. This uses the assumption that
reset_tsf() makes it start at 0, and that then the hardware won't sync
up until N seconds etc. I'd like that to be spelt out here, rather than
having to think about this when reading the comment.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-02-24 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 23:18 [PATCH v3] mac80211: Give it some time to do the TSF sync Alina Friedrichsen
2009-02-24 1:40 ` Johannes Berg [this message]
2009-02-25 0:49 ` Alina Friedrichsen
2009-02-25 0:52 ` Alina Friedrichsen
2009-02-25 1:45 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2009-02-22 17:19 Alina Friedrichsen
2009-02-23 13:46 ` Kalle Valo
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=1235439633.4455.33.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=x-alina@gmx.net \
/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).