From: Felix Fietkau Date: Mon, 28 Jun 2010 12:27:31 +0200 Subject: [ath9k-devel] [RFC/RFT] minstrel_ht: new rate control module for 802.11n In-Reply-To: References: <4B8C3A21.2050105@openwrt.org> <133e8d7e1003020419r6fab7b13kd77b06407c8c1380@mail.gmail.com> <4B8D25DC.8070502@openwrt.org> <133e8d7e1003020747w348dbee0g60a25a86393972d7@mail.gmail.com> <4B8D396B.5040007@openwrt.org> <4C223F58.3060509@openwrt.org> <4C27E8E8.8040606@openwrt.org> Message-ID: <4C287913.8070405@openwrt.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 2010-06-28 12:20 PM, Bj?rn Smedman wrote: > 2010/6/28 Felix Fietkau : >> On 2010-06-28 2:01 AM, Bj?rn Smedman wrote: > [snip] >>> I guess the real solution is your rewrite... But in the mean time >>> perhaps we can memcpy the tx_info control from the last subframe to >>> the first before calling ath_buf_set_rate() in ath_tx_sched_aggr()? >>> Could that have any side effects? It could make the aggregate size go >>> over the 4 ms limit I guess... How bad is that? >> There's an easy solution which would take into account the 4ms frame >> limit properly, and which could work without any memcpy() hacks: >> >> I could just grab a pointer to the last buffer in the tid queue in the >> ath_tx_sched_aggr() function, then pass it to ath_lookup_rate() via >> ath_tx_form_aggr(), and also to ath_buf_set_rate(). Then I make those >> functions use this last buffer as reference for the rate lookup. > > Sounds better to use the rate control from the last buffer in the tid > queue. But be careful if you don't memcpy it to the first frame of the > aggregate then the feedback calculated in ath_tx_rc_status() after tx > will be incorrect again, no? Right. I intend to let ath_buf_set_rate() set the rates array of the first subframe accordingly. - Felix