[Ns-bugs] [Bug 802] Minstrel algorithm causes segmentation fault
code at nsnam.ece.gatech.edu
Wed Apr 21 04:29:08 PDT 2010
--- Comment #15 from Mathieu Lacage <mathieu.lacage at sophia.inria.fr> 2010-04-21 07:29:07 EDT ---
(In reply to comment #14)
> (In reply to comment #13)
> > nak. minstrel is high latency. See my original arf/aarf paper for a definition.
> I guess you mean that the original minstrel in madwifi is high latency, right?
Yes, the original minstrel algorithm, was designed to work on high latency
> (In reply to comment #11)
> > Minstrel does not work properly if it is set to
> > high latency.
> I get the impression that the minstrel implementation in ns-3 is low latency,
> in that you update statistics everytime DoReportDataOk and DoReportDataFailed
> are called. These updated stats are then used for selecting the rate for the
> next transmission attempt.
> Duy, would it be possible to change how stats are updated so that minstrel can
> be high latency as it is in the real world?
> Ideally, if it were possible to support both low and high latency by setting
> the corresponding attribute, it would be great.
I did that at some point for amrr/onoe but it's really hard to get right so, I
would advise against it.
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Ns-bugs