From: Peter Oh <poh@codeaurora.org>
To: Neelansh Mittal <Neelansh@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Adjusting_tbtt in mesh capability
Date: Wed, 03 Feb 2016 15:47:52 -0800 [thread overview]
Message-ID: <56B291A8.4000701@codeaurora.org> (raw)
In-Reply-To: <loom.20160203T210737-307@post.gmane.org>
On 02/03/2016 12:18 PM, Neelansh Mittal wrote:
> Currently, for a mesh node ,the mac80211
> sync implementation sets the tbtt
> adjustment bit , when it is adjusting it's
> tsf as part of Neighbour offset
> Synchronization(Function:mesh_sync_offset_
> adjust_tbtt())
> According to ieee80211s specification,
> this bit should(only) be set when tbtt
> adjustment procedure(as part of tbtt
> selection/mbca) is ongoing.
> So why does mac80211 set it as part of
> Offset syncronization, ie , what is
> advantage the when a mesh node announces
> that "my tbtt will be delayed" to it's
> peers?
I guess it's to prevent mesh peers from running TBTT adjustment?
Setting TBTT adjustment bit is good idea although the standard is
addressing TBTT adjustment bit during MBCA/TBTT selection procedure,
since the key idea of setting the bit is to run TBTT adjustment by only
one mesh point at a time IMO.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-03 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 20:18 Adjusting_tbtt in mesh capability Neelansh Mittal
2016-02-03 23:47 ` Peter Oh [this message]
2016-02-04 4:06 ` Neelansh Mittal
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=56B291A8.4000701@codeaurora.org \
--to=poh@codeaurora.org \
--cc=Neelansh@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.