Date: Mon, 22 Aug 2011 06:33:03 +0000 (UTC) From: Adrian Chadd <adrian@FreeBSD.org> To: src-committers@freebsd.org, svn-src-user@freebsd.org Subject: svn commit: r225074 - user/adrian/if_ath_tx/sys/dev/ath Message-ID: <201108220633.p7M6X3DS037423@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: adrian Date: Mon Aug 22 06:33:03 2011 New Revision: 225074 URL: http://svn.freebsd.org/changeset/base/225074 Log: Update README. Modified: user/adrian/if_ath_tx/sys/dev/ath/README Modified: user/adrian/if_ath_tx/sys/dev/ath/README ============================================================================== --- user/adrian/if_ath_tx/sys/dev/ath/README Mon Aug 22 06:27:45 2011 (r225073) +++ user/adrian/if_ath_tx/sys/dev/ath/README Mon Aug 22 06:33:03 2011 (r225074) @@ -57,6 +57,7 @@ Things to debug! * drain? Things that need doing! +----------------------- * When off-channel, aggregate traffic should stay queued, but raw frames (eg probes) should be sent? @@ -175,7 +176,30 @@ Hopefully it's something easy * When a node is flushed (but not being deleted) should the BAW also be updated? I don't think it is right now and this could be incorrect. + +Stuff to do to the rate control code +------------------------------------ + +* Teach ath_rate_sample about the packet error rate when TX'ing aggregates + +* Delay rate control lookup? Until the aggregate is being formed or a non-agg + frame is being TXed? + +* .. then we can re-do rate control lookups for retransmits? That should help + with performance issues when bad MCSes have been chosen + +* Tidy up ath_rate_sample and have it use the flags in the ath_rc_series array, + rather than re-calculating what flags are used (ht20/ht40, shortgi, etc.) + + That way if the rate selection logic decides to use something besides what + the node says it supports (eg sending a HT/20 frame to a HT/40 station, + sending long-gi instead of short-GI) then the correct calculations can be + made. + + The rate selection stuff doesn't do this -now-, but it may be useful later. + Fixed issues: +------------- * Recursive TXQ lock on interface destruction:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201108220633.p7M6X3DS037423>