All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Oh <poh@codeaurora.org>
To: Maxim Altshul <maxim.altshul@ti.com>,
	johannes@sipsolutions.net, kvalo@codeaurora.org
Cc: eliad@wizery.com, yanivma@ti.com, guym@ti.com, arik@wizery.com,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [PATCH 0/3] *** Mesh Path Selection Metric Calculation ***
Date: Mon, 20 Jun 2016 17:10:30 -0700	[thread overview]
Message-ID: <576885F6.3010409@codeaurora.org> (raw)
In-Reply-To: <1466427622-5953-1-git-send-email-maxim.altshul@ti.com>

where is 2/3 ?
On 06/20/2016 06:00 AM, Maxim Altshul wrote:
> Hi All,
> This patch series focuses on metric calculation that
> occurs during the path selection phase of a mesh network.
>
> During the path selection phase, the mesh hwmp module
> performs metric calculations, that take as parameters
> the last TX rate that was used for a specific link,
> and the packet error rate.
>
> These parameters should be reported by the FW to the driver
> constantly for the mechanism to work properly.
>
> In case that a vendor offloads the rate control mechanism
> to the FW, these parameters will be rarely updated,
> or updated incorrectly.
>
> This situation causes the mesh hwmp module to calculate incorrect
> metrics and as a consequence, not to choose the best paths possible.
>
>
> This patch series is divided to three patches and does the following:
>
> 1. Modifies mesh hwmp module and allows vendors that offload the
> rate control mechanism to their FW, to report last TX rates and PER
> to the mesh hwmp module by using an existing op called
> get_expected_throughput.
> In case that a vendor does not implement the op, all previous
> functionality still applies.
>
> 2. Implements the opcode and the mechanism that reports the rates
> in TI driver.
>
> Maxim Altshul (3):
>   wlcore/wl18xx: Add functionality to accept TX rate per link
>   wlcore: Add support for get_expected_throughput opcode
>   mac80211: mesh: Add support for HW RC implementation
>
>  drivers/net/wireless/ti/wl18xx/main.c     |  4 ++++
>  drivers/net/wireless/ti/wl18xx/tx.c       | 22 ++++++++++++++++++----
>  drivers/net/wireless/ti/wl18xx/wl18xx.h   |  6 +++++-
>  drivers/net/wireless/ti/wlcore/main.c     | 16 ++++++++++++++++
>  drivers/net/wireless/ti/wlcore/rx.c       |  7 +++++++
>  drivers/net/wireless/ti/wlcore/wlcore_i.h | 13 +++++++++++++
>  net/mac80211/mesh_hwmp.c                  | 23 +++++++++++++++--------
>  7 files changed, 78 insertions(+), 13 deletions(-)
>


WARNING: multiple messages have this Message-ID (diff)
From: Peter Oh <poh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Maxim Altshul <maxim.altshul-l0cyMroinI0@public.gmane.org>,
	johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org,
	kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
Cc: eliad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org,
	yanivma-l0cyMroinI0@public.gmane.org,
	guym-l0cyMroinI0@public.gmane.org,
	arik-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Subject: Re: [PATCH 0/3] *** Mesh Path Selection Metric Calculation ***
Date: Mon, 20 Jun 2016 17:10:30 -0700	[thread overview]
Message-ID: <576885F6.3010409@codeaurora.org> (raw)
In-Reply-To: <1466427622-5953-1-git-send-email-maxim.altshul-l0cyMroinI0@public.gmane.org>

where is 2/3 ?
On 06/20/2016 06:00 AM, Maxim Altshul wrote:
> Hi All,
> This patch series focuses on metric calculation that
> occurs during the path selection phase of a mesh network.
>
> During the path selection phase, the mesh hwmp module
> performs metric calculations, that take as parameters
> the last TX rate that was used for a specific link,
> and the packet error rate.
>
> These parameters should be reported by the FW to the driver
> constantly for the mechanism to work properly.
>
> In case that a vendor offloads the rate control mechanism
> to the FW, these parameters will be rarely updated,
> or updated incorrectly.
>
> This situation causes the mesh hwmp module to calculate incorrect
> metrics and as a consequence, not to choose the best paths possible.
>
>
> This patch series is divided to three patches and does the following:
>
> 1. Modifies mesh hwmp module and allows vendors that offload the
> rate control mechanism to their FW, to report last TX rates and PER
> to the mesh hwmp module by using an existing op called
> get_expected_throughput.
> In case that a vendor does not implement the op, all previous
> functionality still applies.
>
> 2. Implements the opcode and the mechanism that reports the rates
> in TI driver.
>
> Maxim Altshul (3):
>   wlcore/wl18xx: Add functionality to accept TX rate per link
>   wlcore: Add support for get_expected_throughput opcode
>   mac80211: mesh: Add support for HW RC implementation
>
>  drivers/net/wireless/ti/wl18xx/main.c     |  4 ++++
>  drivers/net/wireless/ti/wl18xx/tx.c       | 22 ++++++++++++++++++----
>  drivers/net/wireless/ti/wl18xx/wl18xx.h   |  6 +++++-
>  drivers/net/wireless/ti/wlcore/main.c     | 16 ++++++++++++++++
>  drivers/net/wireless/ti/wlcore/rx.c       |  7 +++++++
>  drivers/net/wireless/ti/wlcore/wlcore_i.h | 13 +++++++++++++
>  net/mac80211/mesh_hwmp.c                  | 23 +++++++++++++++--------
>  7 files changed, 78 insertions(+), 13 deletions(-)
>

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-06-21  0:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 13:00 [PATCH 0/3] *** Mesh Path Selection Metric Calculation *** Maxim Altshul
2016-06-20 13:00 ` Maxim Altshul
2016-06-20 13:00 ` [PATCH 1/3] wlcore/wl18xx: Add functionality to accept TX rate per link Maxim Altshul
2016-06-20 13:00   ` [PATCH 2/3] wlcore: Add support for get_expected_throughput opcode Maxim Altshul
2016-06-20 13:00     ` Maxim Altshul
2016-06-20 13:00     ` [PATCH 3/3] mac80211: mesh: Add support for HW RC implementation Maxim Altshul
2016-06-21  9:18       ` Johannes Berg
2016-06-21  9:18         ` Johannes Berg
2016-06-21  0:10 ` Peter Oh [this message]
2016-06-21  0:10   ` [PATCH 0/3] *** Mesh Path Selection Metric Calculation *** Peter Oh
2016-06-21  6:18   ` Kalle Valo
2016-06-21 12:19 ` Bob Copeland
2016-06-21 12:19   ` Bob Copeland
2016-06-21 12:23   ` Machani, Yaniv
2016-06-21 12:23     ` Machani, Yaniv

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=576885F6.3010409@codeaurora.org \
    --to=poh@codeaurora.org \
    --cc=arik@wizery.com \
    --cc=davem@davemloft.net \
    --cc=eliad@wizery.com \
    --cc=guym@ti.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maxim.altshul@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=yanivma@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.