From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] station management complexity reduction
Date: Wed, 14 Dec 2011 14:03:38 +0100 [thread overview]
Message-ID: <20111214130338.347106528@sipsolutions.net> (raw)
The complexity of locking in sta_info.c has bothered
me for a while, and it would not have been possible to
inform drivers of station state in a sleeping callback
from IBSS anyway.
Make IBSS not add the stations in RX context, and thus
reduce complexity in sta_info and actually make the new
sta_info_move_state() sleeping.
johannes
next reply other threads:[~2011-12-14 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 13:03 Johannes Berg [this message]
2011-12-14 13:03 ` [PATCH 1/2] mac80211: delay IBSS station insertion Johannes Berg
2011-12-15 10:17 ` [PATCH v2 " Johannes Berg
2011-12-14 13:03 ` [PATCH 2/2] mac80211: reduce station management complexity Johannes Berg
2011-12-15 10:24 ` [PATCH v2 " 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=20111214130338.347106528@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).