Return-path: Received: from dakia2.marvell.com ([65.219.4.35]:39876 "EHLO dakia2.marvell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936078Ab0GPJRa (ORCPT ); Fri, 16 Jul 2010 05:17:30 -0400 Message-ID: <4C402360.5050502@marvell.com> Date: Fri, 16 Jul 2010 14:46:16 +0530 From: yogeshp MIME-Version: 1.0 To: "Luis R. Rodriguez" Cc: Pradeep Nemavat , Nishant Sarmukadam , "linville@tuxdriver.com" , "linux-wireless@vger.kernel.org" Subject: Re: [RFC] mac80211: indicate BA window size with IEEE80211_AMPDU_TX_OPERATIONAL drv_ampud_action References: <4C3F0AA3.4050706@marvell.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Luis, Please see inline comments Luis R. Rodriguez wrote: > On Thu, Jul 15, 2010 at 6:18 AM, yogeshp wrote: >> BA window size for a successful BA setup is not made available to the driver by >> mac80211. The patch below gets the BA window size from addba response and >> indicates it to driver through IEEE80211_AMPDU_TX_OPERATIONAL drv_ampdu_action. > But why do you want that? Your patch and commit log do not mention why > you need this. BA window size from ADDBA response defines how many outstanding MPDUs are allowed for the BA stream by recipient. Since ADDBA response is processed in mac80211 stack, mac80211 should communicate the BA window size to driver (and may be from driver it is further communicated to firmware/hardware) to control the number of outstanding MPDUs while transmitting MPDUs for the stream. > When I compile mac80211 with your patch it fails compilation I do not see this compilation error, I think the patch did not apply cleanly. I will send out another patch without extra white spaces that should solve the compilation issue. If the change is fine, we can then send patches to fix the compilation issues for other drivers too. Thanks Yogesh