From: Johannes Berg <johannes@sipsolutions.net>
To: agreen@cococorp.com, linux-wireless@vger.kernel.org
Cc: Jesse Jones <jjones@cococorp.com>
Subject: Re: [PATCH v2] mac80211: Jitter HWMP MPATH reply frames to reduce collision on dense networks.
Date: Thu, 16 Mar 2017 11:18:50 +0100 [thread overview]
Message-ID: <1489659530.2370.10.camel@sipsolutions.net> (raw)
In-Reply-To: <58B09082.7020704@cococorp.com> (sfid-20170224_205905_277542_E6C0402D)
Sorry - this is the other half of my reply that I accidentally deleted
before sending...
> +static void flush_tx_skbs(struct ieee80211_sub_if_data *sdata)
> +{
> + struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh;
> + struct mesh_tx_queue *tx_node;
> +
> + spin_lock_bh(&ifmsh->mesh_tx_queue_lock);
> +
> + /* Note that this check is important because of the two-
> stage
> + * way that ieee80211_if_mesh is initialized.
> + */
I think you should fix that rather than work around it. If this is
called with iftype != mesh then this is super problematic anyway, since
ifmsh->tx_queue_len would alias some other variable (there's a union).
> + if (ifmsh->tx_queue_len > 0) {
> + mhwmp_dbg(sdata, "flushing %d skbs", ifmsh-
> >tx_queue_len);
> +
> + while (!list_empty(&ifmsh->tx_queue.list)) {
> + tx_node = list_last_entry(&ifmsh-
> >tx_queue.list,
> + struct
> mesh_tx_queue, list);
> + kfree_skb(tx_node->skb);
> + list_del(&tx_node->list);
> + kfree(tx_node);
> + }
> + ifmsh->tx_queue_len = 0;
> + }
> +
> + spin_unlock_bh(&ifmsh->mesh_tx_queue_lock);
> +}
All of this also gets *vastly* simpler if it's just skb_queue_purge()
:)
> + spin_lock_bh(&ifmsh->mesh_tx_queue_lock);
> +
> + list_for_each_entry(tx_node, &ifmsh->tx_queue.list, list) {
> + ieee80211_tx_skb(sdata, tx_node->skb);
> + }
I don't think you should hold the lock across _tx_skb(), ISTR problems
with that - particularly with the STA lock, so this might be OK, but it
might also cause lock ordering issues. It's easy to avoid anyway, so
better not to do it.
johannes
next prev parent reply other threads:[~2017-03-16 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 19:58 [PATCH v2] mac80211: Jitter HWMP MPATH reply frames to reduce collision on dense networks Alexis Green
2017-02-27 13:30 ` Johannes Berg
2017-02-27 20:10 ` Alexis Green
2017-03-02 8:36 ` Johannes Berg
2017-03-02 17:41 ` Jesse Jones
2017-03-06 12:38 ` Johannes Berg
2017-03-06 18:01 ` Jesse Jones
2017-03-09 15:49 ` Matthias May
2017-03-10 8:40 ` Kalle Valo
2017-03-10 15:24 ` Alexis Green
2017-03-13 15:49 ` Benjamin Beichler
2017-03-14 13:45 ` Johannes Berg
2017-03-20 16:41 ` Thomas Pedersen
2017-03-16 10:16 ` Johannes Berg
2017-03-16 10:18 ` Johannes Berg [this message]
2017-03-19 1:48 ` Alexis Green
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=1489659530.2370.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=agreen@cococorp.com \
--cc=jjones@cococorp.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).