From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, kevinhayes@google.com,
julanhsu@google.com, Rajkumar Manoharan <rmanohar@codeaurora.org>
Subject: [PATCH 0/2] wireless: Add support to probe unexercised mesh link
Date: Thu, 14 Feb 2019 05:56:08 -0800 [thread overview]
Message-ID: <1550152570-13051-1-git-send-email-rmanohar@codeaurora.org> (raw)
Consider below mesh topology.
MP1
/ \
/ \
MP2 --- MP3
Assume that even though MP1 & MP3 have direct mesh links, the path was
established via MP2. (MP1 <-> MP2 <-> MP3). The 1-hop mesh link MP1 <-> MP3
never be excercised till the current path is terminated. As of now, there
is no option to send data frame to pick other than primary path. So mesh
link metric between MP1 & MP3 never be updated. This series allows user
to send data to 1-hop mesh peers through unexercised mesh path.
-Rajkumar
Rajkumar Manoharan (2):
cfg80211: add support to probe unexercised mesh link
mac80211: probe unexercised mesh links
include/net/cfg80211.h | 6 ++++
include/net/mac80211.h | 2 ++
include/uapi/linux/nl80211.h | 15 ++++++++++
net/mac80211/cfg.c | 1 +
net/mac80211/ieee80211_i.h | 6 ++--
net/mac80211/mesh_hwmp.c | 4 +++
net/mac80211/tdls.c | 2 +-
net/mac80211/tx.c | 66 +++++++++++++++++++++++++++++++++++++++-----
net/wireless/nl80211.c | 45 ++++++++++++++++++++++++++++++
net/wireless/rdev-ops.h | 12 ++++++++
net/wireless/trace.h | 19 +++++++++++++
11 files changed, 168 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2019-02-14 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:56 Rajkumar Manoharan [this message]
2019-02-14 13:56 ` [PATCH 1/2] cfg80211: add support to probe unexercised mesh link Rajkumar Manoharan
2019-02-15 10:45 ` Johannes Berg
2019-02-14 13:56 ` [PATCH 2/2] mac80211: probe unexercised mesh links Rajkumar Manoharan
2019-02-15 10:44 ` Johannes Berg
2019-02-17 15:56 ` Rajkumar Manoharan
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=1550152570-13051-1-git-send-email-rmanohar@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=julanhsu@google.com \
--cc=kevinhayes@google.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).