RDKB-64918: [MLO] WiFI Blaster enhancements to support throughput calculations of MLO clients#1168
Merged
Merged
Conversation
…culations of MLO clients Reason for change: Implement blaster trhoughput calculation for multilink clients - Added detection of MLO client for blaster targets - Added logic to start blast on MAP (BCM specific), no traffic is generated otherwise for mlo clients - Added stats monitoring of all valid links in case of MultiLink - Reworked sampling logic to store stats per link per sample - Improved throughput calculation logic to calculate per link througput, the sum of all links tput is the result tput for MLO client Test Procedure: 1) Configure MLO (currently 210 config) 2) Connect MLO client 3) Start blasting via webapp or manually with following commands dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.WifiClient.ActiveMeasurements.Enable bool true dmcli eRT setv Device.WiFi.X_RDKCENTRAL-COM_Report.WifiClient.ActiveMeasurements.Plan.PlanID string a82d191b187241028acb747fe4a029001 dmcli eRT setv Device.WiFi.X_RDKCENTRAL-COM_Report.WifiClient.ActiveMeasurements.Plan.Step.1.StepID uint 0 dmcli eRT setv Device.WiFi.X_RDKCENTRAL-COM_Report.WifiClient.ActiveMeasurements.Plan.Step.1.DestMac string 8876B9F27B8D dmcli eRT setv Device.WiFi.X_RDKCENTRAL-COM_Report.WifiClient.ActiveMeasurements.Enable bool true 4) Check overall calculated tput in webapp or manually via /tmp/wifiBlaster logs Risks: Medium Priority: P1 Signed-off-by: Vitaliy Lyashenko <v.for.vitalik@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the WiFi Blaster active measurement flow to support Multi-Link Operation (MLO) clients by collecting per-link stats and computing overall throughput as the sum across links.
Changes:
- Extend blaster sample storage to keep packet counters per link (per radio) instead of a single counter.
- Detect MLO clients and track multiple associated VAP indices (including BCM MAP handling) for a single target client.
- Update sampling and throughput calculation to aggregate per-link deltas into total throughput for MLO clients.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| source/apps/blaster/wifi_blaster.h | Expands frame counter samples to arrays indexed per link/radio. |
| source/apps/blaster/wifi_blaster.c | Adds MLO detection, multi-VAP sampling configuration, per-link sample capture, and aggregated throughput computation. |
| include/wifi_base.h | Extends active_msmt_step_t to carry MLO flag and additional VAP indices for MLO links. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
narendradandu
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reason for change:
Implement blaster trhoughput calculation for multilink clients
Test Procedure:
Risks: Medium
Priority: P1