linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <me@bobcopeland.com>
Cc: Sven Eckelmann <sven@narfation.org>,
	linux-wireless@vger.kernel.org, Felix Fietkau <nbd@openwrt.org>,
	Sven Eckelmann <sven@open-mesh.com>,
	Arik Nemtsov <arik@wizery.com>,
	liad.kaufman@intel.com
Subject: Re: [RFC v3] mac80211: lock rate control
Date: Tue, 14 Apr 2015 09:54:19 +0200	[thread overview]
Message-ID: <1428998059.3019.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20150413212628.GA7869@localhost> (sfid-20150413_232633_258914_B093F402)

On Mon, 2015-04-13 at 17:26 -0400, Bob Copeland wrote:

> mac80211: introduce plink lock for plink fields
> 
> The mesh plink code uses sta->lock to serialize access to the
> plink state fields between the peer link state machine and the
> peer link timer.  Some paths (e.g. those involving
> mps_qos_null_tx()) unfortunately hold this spinlock across
> frame tx, which is soon to be disallowed.  Add a new spinlock
> just for plink access.
> 
> Signed-off-by: Bob Copeland <me@bobcopeland.com>

Thank you!

I've applied both this and the rate control locking patch.

We may later want to pick that up for stable perhaps, but let's let it
bake a little longer, it's pretty big.

johannes


      reply	other threads:[~2015-04-14  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  8:14 [RFC v3] mac80211: lock rate control Sven Eckelmann
2015-03-11  8:22 ` Sven Eckelmann
2015-03-12 18:37 ` Johannes Berg
2015-04-13 21:26   ` Bob Copeland
2015-04-14  7:54     ` Johannes Berg [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=1428998059.3019.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arik@wizery.com \
    --cc=liad.kaufman@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=nbd@openwrt.org \
    --cc=sven@narfation.org \
    --cc=sven@open-mesh.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).