Date: Fri, 19 Aug 2011 07:21:19 +0000 (UTC) From: Adrian Chadd <adrian@FreeBSD.org> To: src-committers@freebsd.org, svn-src-user@freebsd.org Subject: svn commit: r224998 - user/adrian/if_ath_tx/sys/dev/ath Message-ID: <201108190721.p7J7LJhU092413@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: adrian Date: Fri Aug 19 07:21:19 2011 New Revision: 224998 URL: http://svn.freebsd.org/changeset/base/224998 Log: Note some more things to look at. 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 Fri Aug 19 07:12:50 2011 (r224997) +++ user/adrian/if_ath_tx/sys/dev/ath/README Fri Aug 19 07:21:19 2011 (r224998) @@ -34,6 +34,17 @@ Things that need doing! one was used? - what else would be helpful? +* Am I too aggressively scheduling things, and thus the aggregation code + doesn't ever get a chance to form decent sized aggregates? + +* I'm getting a lot of OOR packets at the receive end, is this because + of a large number of software retries? or is it that, combined with + TX'ing a long list of aggregates that mostly fill the BAW, meaning + packets can stay out of order for longer (but still be within the BAW?) + I bet this'd piss off TCP, if it had to wait for 20/30 packets + before it received the next retransmit (and thus the AMPDU RX queue + would get flushed.) + Things that need investigating! There's a crash which occurs when a wlan interface is destroyed and
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201108190721.p7J7LJhU092413>