Return-path: Received: from dhost002-46.dex002.intermedia.net ([64.78.21.140]:42088 "EHLO dhost002-46.dex002.intermedia.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965320AbXDLAS5 convert rfc822-to-8bit (ORCPT ); Wed, 11 Apr 2007 20:18:57 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [patch 2/5] Add basic support for IEEE 802.11n discovery and association Date: Wed, 11 Apr 2007 17:20:11 -0700 Message-ID: In-Reply-To: <1ba2fa240704111605l305230d3vf09c085473364eb3@mail.gmail.com> References: <1174909105.1364.53.camel@dell-4965.jf.intel.com> <20070411194059.GA2436@tuxdriver.com> <461D3F48.70004@linux.intel.com> <200704111630.06160.flamingice@sourmilk.net> <1ba2fa240704111503l6dcef504na73c997ae75ebccd@mail.gmail.com> <1ba2fa240704111605l305230d3vf09c085473364eb3@mail.gmail.com> From: "Simon Barber" To: "Tomas Winkler" Cc: "Michael Wu" , "mabbas" , "John W. Linville" , , "Jouni Malinen" Sender: linux-wireless-owner@vger.kernel.org List-ID: There are several possible notification mechanisms - according to the application's needs. It could be part of tc - using a qdisc, or libpcap, or something hardwired into mac80211 or something else. Someone might want this controlled by a userspace application (e.g. video streaming). Someone else might want an automatic algorithm. Simon -----Original Message----- From: Tomas Winkler [mailto:tomasw@gmail.com] Sent: Wednesday, April 11, 2007 4:05 PM To: Simon Barber Cc: Michael Wu; mabbas; John W. Linville; linux-wireless@vger.kernel.org; Jouni Malinen Subject: Re: [patch 2/5] Add basic support for IEEE 802.11n discovery and association So you monitor your traffic load in driver, then notify user space application which opens or tears down for you the BA stream? What would be the notification mechanism ? On 4/12/07, Simon Barber wrote: > Setup and tear down of BA should be done by userspace - actual > processing of the BA frames themselves should be done in mac80211. > This allows maximum flexibility from userspace to control the policy > of when to setup and teardown BA streams. > > Simon > > -----Original Message----- > From: Tomas Winkler [mailto:tomasw@gmail.com] > Sent: Wednesday, April 11, 2007 3:04 PM > To: Michael Wu > Cc: mabbas; John W. Linville; linux-wireless@vger.kernel.org; Jouni > Malinen; Simon Barber > Subject: Re: [patch 2/5] Add basic support for IEEE 802.11n discovery > and association > > On 4/11/07, Michael Wu wrote: > > On Wednesday 11 April 2007 16:04, mabbas wrote: > > > I am not familiar with userspace mlme what needed to be done? > > mac80211 has a userspace mlme mode which defers all things dealing > > with management frames to userspace (wpa_supplicant). It basically > > disables all the code in ieee80211_sta.c and routes management > > frames to a special interface where wpa_supplicant (or hostap) > > handles things. This is preferred and the ieee80211_sta.c code is > > there for > backwards compatibility. > > > > No major features should be added to the in-kernel MLME > > (ieee80211_sta.c) but even more importantly, your patch series does > > not provide the appropriate hooks for a userspace MLME to support a > driver using this 802.11n API. > > > > -Michael Wu > > > > > Meanwhile I don't see feasible user space implementation for this as > data packet classification is done in kernel. BACK streams are > dynamically opened and teared down per TID according current traffic > shape. > This is new feature and the user space handling is not well understand > yet. I suggest that we proceed with patches and let the evolution > making its steps. > > If someone has concrete suggestion on implementing it as user space > MLME I will be glad to hear. > Thanks > > > Tomas >