Changes between Version 8 and Version 9 of Internal/WinlabMadwifi/PipelineMACPaper


Ignore:
Timestamp:
Nov 15, 2005, 8:22:52 PM (19 years ago)
Author:
zhibinwu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/WinlabMadwifi/PipelineMACPaper

    v8 v9  
    3939== Experiment Evaluation ==
    4040
    41 using 2 nodes and 1 AP, configure 1 node to have twice bandwidth as another node (interferer/competitor)
     41using 2 nodes and 1 AP, configure 1 node to have twice bandwidth as another node (interferer/competitor). All use NETGEAR cards (Atheros-chip).
    4242
    4343== Weakness ==
     
    4848
    4949== Disucussion ==
    50  1. Is a kernel patch a good approach?
    51  1. 10ms scheduling resolution, good enough?
     50 1. Is a kernel patch a good approach? The kernel & driver are difficult to develop. As long as the software can be stablized, it is a feasible approach.
     51 1. 10ms scheduling resolution, good enough? No. Schedule too many packets in a batch. It's better to use HW timer, a 64-bit timing counter in Atheros chip.
    5252
    5353