Bug 674 – EIFS is not handled correctly in DcfManager::GetAccessGrantStart

Bug 674 - EIFS is not handled correctly in DcfManager::GetAccessGrantStart


Summary:	EIFS is not handled correctly in DcfManager::GetAccessGrantStart

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	wifi
Version:	ns-3-dev
Hardware:	All All

Importance:	P2 normal
Assigned To:	Mathieu Lacage

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-10 05:30 UTC by Kirill Andreev
Modified:	2009-11-30 07:21 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Proposed fix (532 bytes, patch) 2009-09-10 05:30 UTC, Kirill Andreev	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

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

Description Kirill Andreev 2009-09-10 05:30:24 UTC

Created attachment 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 Mathieu Lacage 2009-11-16 09:59:32 UTC

The patch looks good. If you have a test in dcf-manager-test.cc for this, you can commit.

Comment 2 Mathieu Lacage 2009-11-30 07:21:57 UTC

changeset 5629104d7747