From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mga09.intel.com ([134.134.136.24]:18275 "EHLO mga09.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755370Ab1KNV26 (ORCPT <rfc822;linux-wireless@vger.kernel.org>);
	Mon, 14 Nov 2011 16:28:58 -0500
Subject: Re: iwlagn 3.0.9 aggreggation messages
From: wwguy <wey-yi.w.guy@intel.com>
To: Lars Schotte <gusto@guttok.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
In-Reply-To: <20111114221847.2ca32e6a@hana.gusto>
References: <20111114131642.31e8ddbd@hana.gusto>
	 <1321283410.13578.33.camel@wwguy-ubuntu>
	 <20111114201947.58d5fdf6@hana.gusto>	<1321303101.1796.8.camel@wwguy-ubuntu>
	 <20111114221847.2ca32e6a@hana.gusto>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 14 Nov 2011 13:22:30 -0800
Message-ID: <1321305750.1796.11.camel@wwguy-ubuntu> (sfid-20111114_222902_749732_79F50E3C)
Mime-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

ok, there were changes in this area to trigger faster in order to
address some performance issue. 

so I believe more logic need to go in and delay the trigger in some
cases.

Would you be able to test for me if I have a patch for testing?

Thanks
Wey

On Mon, 2011-11-14 at 13:18 -0800, Lars Schotte wrote:
> of course he deactivates the aggregation soon after, because the AP
> sees no reason why there should be one.
> 
> triggering the aggreggation is that problem and it exists only since
> 3.0.9. 3.0.8 is OK, but 3.1.1 seems to be affected as well. 3.1.0 was
> OK.
> 
> so someting broke it recently.
> 
> unfortunately i can not remember if 3.2 kernel had that problem, i
> already removed it because it was too unstable for me, so i can not
> test it any more (w/o compiling it again).
> 
> On Mon, 14 Nov 2011 12:38:21 -0800
> wwguy <wey-yi.w.guy@intel.com> wrote:
> 
> > Hi Schotte,
> > 
> > looks like driver has problem activate the aggregation, you can see in
> > the log, the aggregation queue being activate then deactivate soon
> > after. that is why you are seeing the messages showing up in dmesg
> > log.
> > 
> > what AP you are using? is similar thing happen if you connect to
> > different AP?
> > 
> > Thanks
> > Wey
> 
>