From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: Benoit Papillault <benoit.papillault@free.fr>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: Improved IBSS merges
Date: Mon, 15 Feb 2010 15:44:38 +0100 [thread overview]
Message-ID: <1266245078.5081.23.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100215134023.GA11947@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Mon, 2010-02-15 at 15:40 +0200, Jouni Malinen wrote:
> On Mon, Feb 15, 2010 at 12:33:54AM +0100, Benoit Papillault wrote:
> > According to $11.1.4 from IEEE 802.11-2007, TSF is reset
> (drv_reset_tsf)
> > on MLME-JOIN, ie only when a new IBSS is created or if an existing
> IBSS
> > is joined, but not on IBSS merges.
>
> While that may indeed be what the standard says, drv_reset_tsf() may
> be
> needed to allow the driver to actually learn the new timestamp
> correctly
> in the case of merge. Have you verified that the drivers that support
> IBSS do indeed update their timestamps without that call in case there
> is a large difference in the timestamp values that the separate IBSSes
> used before the merge?
Good point. Also, it shouldn't hurt to always reset it, so what's the
point?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2010-02-15 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 23:33 [PATCH 1/2] mac80211: Improved IBSS merges Benoit Papillault
2010-02-14 23:33 ` [PATCH 2/2] mac80211: Improved IBSS merges even if BSSID is the same Benoit Papillault
2010-02-15 9:28 ` Johannes Berg
2010-02-15 22:24 ` Benoit PAPILLAULT
2010-02-15 9:29 ` Johannes Berg
2010-02-15 13:40 ` [PATCH 1/2] mac80211: Improved IBSS merges Jouni Malinen
2010-02-15 14:44 ` 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=1266245078.5081.23.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benoit.papillault@free.fr \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
/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).