All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, Jouni Malinen <j@w1.fi>,
	Michael Wu <flamingice@sourmilk.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Kernelspace --> Userspace MLME move and related items
Date: Sat, 29 Sep 2007 12:17:40 -0400	[thread overview]
Message-ID: <20070929161740.GB6130@tuxdriver.com> (raw)
In-Reply-To: <1191066581.22960.55.camel@johannes.berg>

On Sat, Sep 29, 2007 at 01:49:41PM +0200, Johannes Berg wrote:
> On Fri, 2007-09-28 at 20:25 -0400, Luis R. Rodriguez wrote:

> > * Should umlme be optional or is this desired mandatory down the road?
> 
> It'll be mandatory for anything that we don't currently do in the
> kernel, which will probably include
>  * 802.11r (fast roaming)
>  * 802.11s (mesh networking) (not entirely sure what management stuff
>    this includes)
>  * 802.11w (encrypted management)
>  * DLS features of 802.11e
>  * ... more I'm not thinking of right now

Can you elaborate some on why you think umlme is required for these
(or other) functions?  It isn't obvious to me that all of these MLME
functions are so complex as to require userland implementations.

Forgive my skepticisim, but in the past umlme has been used as a
religious hammer.   I don't want to keep apparently working/workable
code out of the kernel just because someone thinks currently
non-existant umlme code would be a better solution.

Lacking a mature umlme implementation in-hand, I'm not prepared
to accept a preemptive veto on kmlme extensions without seeing the
code first.

John
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2007-09-29 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29  0:25 Kernelspace --> Userspace MLME move and related items Luis R. Rodriguez
2007-09-29 11:28 ` Johannes Berg
2007-09-29 11:49 ` Johannes Berg
2007-09-29 12:27   ` userspace mlme configuration (was: Kernelspace --> Userspace MLME move and related items) Johannes Berg
2007-09-29 12:54     ` Johannes Berg
2007-10-01 14:06     ` Dan Williams
2007-09-29 16:17   ` John W. Linville [this message]
2007-09-30  8:43     ` Kernelspace --> Userspace MLME move and related items Johannes Berg
2007-10-03  2:50       ` Jouni Malinen
2007-10-03 16:32         ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070929161740.GB6130@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=flamingice@sourmilk.net \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.