Bug 674 - EIFS is not handled correctly in DcfManager::GetAccessGrantStart
: EIFS is not handled correctly in DcfManager::GetAccessGrantStart
Status: RESOLVED FIXED
: ns-3
wifi
: ns-3-dev
: All All
: P2 normal
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-09-10 05:30 EDT by
Modified: 2009-11-30 07:21 EDT (History)


Attachments
Proposed fix (532 bytes, patch)
2009-09-10 05:30 EDT, Kirill Andreev
Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-09-10 05:30:24 EDT
Created an attachment (id=584) [details]
Proposed fix

When the last receive was OK, we say, tat access grant start is m_lastRxEnd +
m_sifs. When we call GetAccessGrantStartFor (), we add Aifsn * m_slotTime. So,
we start to calculate backoff AIFS later after rxEnd.

When the last receive was not ok, we may start to calculate backoff EIFS after
rxEnd.
In GetAccessGrantStart we add EifsNoDifs to last Rx end. In
GetAxxessGrantStartFor () we add as in previous case Aifsn * m_slotTime. So,
instead real EIFS we wait EIFS-SIFS
------- Comment #1 From 2009-11-16 09:59:32 EDT -------
The patch looks good. If you have a test in dcf-manager-test.cc for this, you
can commit.
------- Comment #2 From 2009-11-30 07:21:57 EDT -------
changeset 5629104d7747