From: Michael Buesch <mb@bu3sch.de>
To: "Andy Johnson" <johnsonzjo@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211 MLME and user space
Date: Wed, 19 Nov 2008 16:45:58 +0100 [thread overview]
Message-ID: <200811191645.58844.mb@bu3sch.de> (raw)
In-Reply-To: <147a89290811181216i66a5a22cv77e6d06180b7b312@mail.gmail.com>
On Tuesday 18 November 2008 21:16:49 Andy Johnson wrote:
> My question is : why?
It's really similiar to the questions:
Why do we have udev? Why didn't we fix devfs instead?
Or why is hotplugging in userspace?
It's all basically, because we don't _need_ to have it in the kernel.
Having it in userspace means much easier code (often no locking needed).
Having it in userspace means, it's easily runtime replacable. Even after
crashes.
Having it in userspace means exploitable bugs are less likely to affect
the whole system.
There probably are a lot more reasons to do this.
--
Greetings Michael.
prev parent reply other threads:[~2008-11-19 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:16 mac80211 MLME and user space Andy Johnson
2008-11-18 23:25 ` Johannes Berg
2008-11-19 15:45 ` Michael Buesch [this message]
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=200811191645.58844.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johnsonzjo@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).