On Tue, Mar 15, 2011 at 11:41 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2011-03-15 at 11:16 -0700, Daniel Halperin wrote: > >> There's still something off about the window size: unlike with ath9k, >> the receiver does continually print out warnings about advancing its >> window. There's something very fishy here: for any given aggregation >> session, the part of the sequence number space this happens is always >> the same! Really weird. Here's a log from 3 agg sessions in a row, >> just running simple TCP iperf: >> >> [341221.679710] New seq exceeds buffering window: 283, 250 > > Ok thanks for the patch, I'll still reply here though. > > >> [341398.950019] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = >> 00:16:ea:c3:b3:8e tid = 0 >> [341401.790964] New seq exceeds buffering window: 2335, 2304 > > So the delta is always 31, it seems? Is iwlwifi consistently sending > batches of 32 instead of the advertised 31? I don't think that's the case, in fact I've never seen the hardware send a larger batch than frame limit. I think it's from a missed frame early in one batch being pushed out by a late frame in the next batch. I know how to get the logs to find out. I have a bunch of meetings soon, but I'll dig into this more later. > Also -- don't get confused, the tx_agg_start is on its own TX agg > session, but the new seq stuff is on its RX agg session. You're absolutely true; but both sides pretty much start and stop aggregation in sync, they both have the same timeouts and I'm only using tcp traffic which is bidirectional. They're running the same software on the same hardware, modulo one being an AP and one a client. [Yes, I know that AP mode is broken on the iwl5300 but I disable power save, etc., and it seems to work well enough ... Actually, does AP (not P2P) mode work properly on the P2P-supporting 6300? I could switch to using those.] Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
