From: Johannes Berg <johannes@sipsolutions.net>
To: Rajkumar Manoharan <rmanohar@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, kevinhayes@google.com,
julanhsu@google.com
Subject: Re: [PATCH 1/2] cfg80211: add support to probe unexercised mesh link
Date: Fri, 15 Feb 2019 11:45:25 +0100 [thread overview]
Message-ID: <a6fd97757fe5254b60556035da5ffcc42e539c38.camel@sipsolutions.net> (raw)
In-Reply-To: <1550152570-13051-2-git-send-email-rmanohar@codeaurora.org>
> + * @NL80211_CMD_PROBE_MESH_LINK: The requirement for mesh link metric
> + * refreshing, is that from one mesh point we be able to send some data
> + * frames to other mesh points which are not currently selected as a
> + * primary traffic path, but which are only 1 hop away. The absence of
> + * the primary path to the chosen node makes it necessary to apply some
> + * form of marking on a chosen packet stream so that the packets can be
> + * properly steered to the selected node for testing, and not by the
> + * regular mesh path lookup. Further, the packets must be of type data
> + * so that the rate control (often embedded in firmware) is used for
> + * rate selection.
> + *
> + * Uses %NL80211_ATTR_MAC and %NL80211_ATTR_FRAME attributes. The frame
> + * content here is ethernet data.
Please document the address requirements as well.
johannes
next prev parent reply other threads:[~2019-02-15 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:56 [PATCH 0/2] wireless: Add support to probe unexercised mesh link Rajkumar Manoharan
2019-02-14 13:56 ` [PATCH 1/2] cfg80211: add " Rajkumar Manoharan
2019-02-15 10:45 ` Johannes Berg [this message]
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=a6fd97757fe5254b60556035da5ffcc42e539c38.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=julanhsu@google.com \
--cc=kevinhayes@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@codeaurora.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).