From: Denis Kenzior <denkenz@gmail.com>
To: Michael Johnson <mjohnson459@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 1/2] netdev: Add logging for CQM messages
Date: Mon, 1 Aug 2022 10:17:08 -0500 [thread overview]
Message-ID: <6bc199e2-2f40-b192-9de6-30fceb2510ea@gmail.com> (raw)
In-Reply-To: <20220801100631.41605-1-mjohnson459@gmail.com>
Hi Michael,
On 8/1/22 05:06, Michael Johnson wrote:
> Add extra logging around CQM events to help track wifi status.
>
> The signal strength logging matches wpa_supplicant's which looks like
> this:
>
> CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=-96 txrate=6000
> ---
> src/netdev.c | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
<snip>
> @@ -1106,10 +1120,14 @@ static void netdev_cqm_event(struct l_genl_msg *msg, struct netdev *netdev)
> }
>
> if (rssi_event) {
> - if (rssi_val)
> + if (rssi_val) {
> + l_info("Signal change event (above=%d signal=%d)",
I'm not sure 'above=%d' is going to work. rssi_event is only set on
THRESHOLD_EVENT_LOW/THRESHOLD_EVENT_HIGH. If RSSI_LEVEL is being reported, that
pointer is still NULL.
> + *rssi_event, *rssi_val);
> netdev_cqm_event_rssi_value(netdev, *rssi_val);
Hmm, I don't think wpa_s uses RSSI_LEVEL stuff in the kernel, does it? The
reason I ask is that we do have UIs that setup RSSI level reporting for
displaying connection link quality (in number of bars for example). Since such
events are quite common, I think you're going to get quite a bit of spam in the
logs. Are you only interested in cases where the roaming threshold is reached?
If so, you may need to modify netdev_cqm_event_rssi_value() instead.
> - else
> + } else {
> + l_info("Signal change event (above=%d)", *rssi_event);
> netdev_cqm_event_rssi_threshold(netdev, *rssi_event);
> + }
> }
> }
>
Patch 2 looks fine btw, so I applied that one.
Regards,
-Denis
next prev parent reply other threads:[~2022-08-01 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 10:06 [PATCH 1/2] netdev: Add logging for CQM messages Michael Johnson
2022-08-01 10:06 ` [PATCH 2/2] station: Log scan results during a roam Michael Johnson
2022-08-01 15:17 ` Denis Kenzior [this message]
2022-08-01 16:18 ` [PATCH 1/2] netdev: Add logging for CQM messages Michael Johnson
2022-08-01 17:14 ` Denis Kenzior
2022-08-01 18:09 ` Michael Johnson
2022-08-01 18:30 ` Denis Kenzior
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=6bc199e2-2f40-b192-9de6-30fceb2510ea@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=mjohnson459@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox