[Ns-developers] Traced callbacks in WifiPhy
timo.bingmann at student.kit.edu
Fri Jan 9 04:52:44 PST 2009
On Friday 09 January 2009 13:43:23 Mathieu Lacage wrote:
> On Fri, 2009-01-09 at 13:24 +0100, Timo Bingmann wrote:
> > I now like the WifiPhyTag idea much better. But still Tags cannot be
> > updated easily? I mean like updating a field rxPowerDbm.
> No, they can't be updated: once set, you can't change the content unless
> you first remove the tag and then add it back. Doing so will be fairly
> inefficient (the second add will create a copy of all the tags of the
> packet in a new memory buffer) but it will work.
Okay, so the tag must be added only once.
> > > If you both with a patch to do so, yes. It would also be nice to extend
> > > the state machine with a real SYNChronizing state, even if it is not
> > > used in the current codebase.
> > That's what I'm currently working at, thus the confusion. However
> > currently I believe I can manage the changes without the extra
> > PreSYNC/PreRX state, which is preferred because it also requires one
> > Schedule() less.
> I merely suggested to change the WifiPhyStateHelper class to keep track
> of an extra state and a couple of extra state transitions, not to use
> this new state and transitions from YansWifiPhy:
> IDLE -> SYNC, SYNC -> RX and IDLE -> RX
> So, the current code would still perform IDLE->RX but if we improve the
> model later, we can perform IDLE->SYNC->RX
> not a big deal.
Yes, I'll do that now. It's better.
See this: bool WifiPhyStateHelper::m_syncing;
More information about the Ns-developers