linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:16:37 +0100	[thread overview]
Message-ID: <1489659397.2370.8.camel@sipsolutions.net> (raw)
In-Reply-To: <58B09082.7020704@cococorp.com> (sfid-20170224_205905_277542_E6C0402D)

Hi,

So I guess after all the discussion, you should amend the commit log a
bit, certainly at least to mention the hidden-node issue.

Regarding the patch itself, I'm not super happy with how big it is,
some additional comments below:

> +struct mesh_tx_queue {
> +	struct list_head list;
> +	struct sk_buff *skb;
> +};

This seems awkward, what's wrong with using an SKB list (struct
sk_buff_head, skb_queue_* etc)?

> +	/* Spinlock for trasmitted MPATH frames */
> +	spinlock_t mesh_tx_queue_lock;

That would also contain the extra spinlock.

> +	struct mesh_tx_queue tx_queue;

This was always a bad idea, since you never need the skb pointer here -
should've just used struct list_head.

> +	int tx_queue_len;

Also contained in the skb queue.

> +	struct delayed_work tx_work;

I don't really see any value here for a delayed work - a pure timer
would work just as well?

Also, these fields should be in ifmsh, I think?

johannes

  parent reply	other threads:[~2017-03-16 10:16 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 [this message]
2017-03-16 10:18 ` Johannes Berg
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=1489659397.2370.8.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).