Return-path: Received: from ug-out-1314.google.com ([66.249.92.173]:64330 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030319AbXDKWED (ORCPT ); Wed, 11 Apr 2007 18:04:03 -0400 Received: by ug-out-1314.google.com with SMTP id 44so219994uga for ; Wed, 11 Apr 2007 15:04:02 -0700 (PDT) Message-ID: <1ba2fa240704111503l6dcef504na73c997ae75ebccd@mail.gmail.com> Date: Thu, 12 Apr 2007 01:03:57 +0300 From: "Tomas Winkler" To: "Michael Wu" Subject: Re: [patch 2/5] Add basic support for IEEE 802.11n discovery and association Cc: mabbas , "John W. Linville" , linux-wireless@vger.kernel.org, "Jouni Malinen" , "Simon Barber" In-Reply-To: <200704111630.06160.flamingice@sourmilk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed References: <1174909105.1364.53.camel@dell-4965.jf.intel.com> <20070411194059.GA2436@tuxdriver.com> <461D3F48.70004@linux.intel.com> <200704111630.06160.flamingice@sourmilk.net> Sender: linux-wireless-owner@vger.kernel.org List-ID: 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