|
Bugzilla – Full Text Bug Listing |
| Summary: | [contribution] Trace source for MediumBusy event of DcaTxop | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Francesco Malandrino <francesco.malandrino> |
| Component: | wifi | Assignee: | ns-bugs <ns-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | francesco.malandrino, gjcarneiro, mathieu.lacage |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | The patch | ||
|
Description
Francesco Malandrino
2009-02-17 06:45:32 UTC
The trace address is: /NodeList/[i]/DeviceList/[i]/$ns3::WifiNetDevice/Mac/$ns3::NqstaWifiMac/DcaTxop/MediumBusy I pushed a modified version of this patch: changeset: 42c89b271a69 1) I added the same code to Nqap and Adhoc wifi macs 2) I did not push the DcaTxop trace source: it does not seem of wider use beyond yourself. If you feel that the DcaTxop trace source is really of wide use, please, let me know. Ideally, you could describe an example scenario where it could/should be used. Uhm, I added the DcaTxop property as I needed to access its MediumBusy trace source. If the trace source is directly available from the *WifiMac classes, even better. (In reply to comment #3) > If the trace source is directly available from the *WifiMac classes, even > better. No, I just made the DcaTxop available from all *WifiMac classes. |