Mesh TODO: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=== Devel Release N ===
=== Next Release ===


Autonomous operation
Reimplement pending queue as a separate queue from rdy (b100)
* Design

* Implement
Rx Invalid frag should be fixed (b97)
* Test


Real fix for t914 -> joseph
Real fix for t914 -> joseph


Polish MPP scripts
Polish IOCTLs - Note: driver not checked in in Obelix
* auto-generate ANYCAST_MPP_IP
Fix fwt_lookup: it was not showing expired routes. Since those
* recognize interfaces
are used now, we show them.
* update masquerade with latest kernel
Update fwt_add for rate, adapt tests
Update fwt_list for valid, rate, precursor, adapt user tools
Check for own address in fwt_add's (fwd to self?)
Add default accept/deny to blinding table (b104)


=== In the near future ===
Clean-up Power Save Legacy
Too many entries on fwt
Stub functions


Separate wireless extensions ethX and mshX (b83)
Separate wireless extensions ethX and mshX (b83)
* Depends on reliable and independent mesh start
Define attributes mshX should have
* Define attributes mshX should have (with Dan, Marcelo)
Implement
* Implement

MPP scripts to autoconfig
auto-generate ANYCAST_MPP_IP
recognize interfaces
update on package for OLPC and try removing all click

OLPC module: do not Oops on rmmod (t992)

rpm of MPP and lsmesh

=== Devel Release N+1 ===

Autonomous operation
Design
Implement
Test

=== Release N+2 ===

Stability/reliability if don't have fix from joseph

Merge with stable branch

Use Marvell approved command codes for FWT and MESH (b84)


=== In the near future ===


Mesh Beacons (b105)
Mesh Beacons (b105)
Add Mesh IEs to Ad-Hoc beacons to
* Add Mesh IEs to Ad-Hoc beacons to advertise mesh capabilities.
* Known limitation, cannot send beacons in infra.
advertise mesh capabilities.
(known limitation, cannot send
beacons in infra)


Measure Performance
Measure Performance
Improve FWT? Worth it?
* Improve FWT? Worth it?
Route clean-up time. Locks needed?
* Route clean-up time. Locks needed?
Start-up time.
* Start-up time.
* Tune route costs


Slow Down RREQs
Slow Down RREQs.
* Don't trigger many RREQ to the same node before the first one could
RREQ --->
have been resolved.
RREQ --->
.
<--- RREP


Improve Stability/Reliability
Improve Stability/Reliability
Line 78: Line 45:


Mesh auto-start on firmware load (b82)
Mesh auto-start on firmware load (b82)
Investigate netif_carrier_on behavior
* Investigate netif_carrier_on behavior




Per-connection Mesh TTL
Per-connection Mesh TTL

=== Driver Work ===

=== Distribution ===

rpm of MPP, lsmesh and other utils (fwt_list)



=== Legend ===
=== Legend ===
bXX -> bug in cozybit's bugzilla
bXX -> bug in cozybit's bugzilla

tXX -> ticket in dev.laptop.org
tXX -> [http://dev.laptop.org/query ticket in trac]

Latest revision as of 16:00, 9 April 2007

Next Release

Autonomous operation

  • Design
  • Implement
  • Test

Real fix for t914 -> joseph

Polish MPP scripts

  • auto-generate ANYCAST_MPP_IP
  • recognize interfaces
  • update masquerade with latest kernel

In the near future

Separate wireless extensions ethX and mshX (b83)

  • Depends on reliable and independent mesh start
  • Define attributes mshX should have (with Dan, Marcelo)
  • Implement

Mesh Beacons (b105)

  • Add Mesh IEs to Ad-Hoc beacons to advertise mesh capabilities.
  • Known limitation, cannot send beacons in infra.

Measure Performance

  • Improve FWT? Worth it?
  • Route clean-up time. Locks needed?
  • Start-up time.
  • Tune route costs

Slow Down RREQs.

  • Don't trigger many RREQ to the same node before the first one could

have been resolved.

Improve Stability/Reliability

Support for Monitor Mode (t886)

Wake-on-WLAN

Tune mesh parameters (t968)

Battery aware routing

Mesh auto-start on firmware load (b82)

  • Investigate netif_carrier_on behavior


Per-connection Mesh TTL

Driver Work

Distribution

rpm of MPP, lsmesh and other utils (fwt_list)


Legend

bXX -> bug in cozybit's bugzilla

tXX -> ticket in trac