All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed

From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>,
	Simonas Kazlauskas <iwd.lists.linux.dev@kazlauskas.me>
Cc: iwd@lists.linux.dev
Subject: Re: Is the data rate estimation for 5GHz channels overly pessimistic?
Date: Tue, 24 Oct 2023 05:32:58 -0700	[thread overview]
Message-ID: <9e12bf94-aa83-4fe6-b045-8dab45b264ae@gmail.com> (raw)
In-Reply-To: <29094eca-dcf8-4234-8afc-13d37db8450c@gmail.com>

Hi Denis/Simonas,

> 
> Now the question is, how do we make sure iwd is estimating the HE rate 
> if available?  Also, how do we tweak the estimation logic with 
> sensitivity numbers (obtained from a spec sheet, or through 
> experimentation) for specific hardware being used.

Trying to catalog different hardware performance and act on it for 
ranking is an impossible task :)

The only simple solution I can think of would be to add a user-option 
for some threshold RSSI in the rate calculation. If set and the RSSI is 
below the lowest of ht_vht_he_base_rssi just use the last index (-82) 
(and maybe force a 20MHz channel width?). This would at least let the 
rate logic return _something_, albeit maybe not accurate. But again, 
those RSSI thresholds were sorta made up anyways :)

So you could set:
[Rank].LowSignalRateThreshold=-90

Any RSSI between -82 and -90 would use -82 for the rank calculation. No 
idea how this would play out in practice, but its at least simple and 
not tied to any given hardware.

Thanks,
James

> 
> Regards,
> -Denis

next prev parent reply	other threads:[~2023-10-24 12:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14  9:23 Is the data rate estimation for 5GHz channels overly pessimistic? Simonas Kazlauskas
2023-10-14 16:02 ` James Prestwood
2023-10-14 17:36   ` Denis Kenzior
2023-10-14 17:45     ` Simonas Kazlauskas
2023-10-14 18:07       ` Denis Kenzior
2023-10-15 19:40         ` Simonas Kazlauskas
2023-10-16 11:35           ` James Prestwood
2023-10-16 12:38             ` James Prestwood
2023-10-16 19:12               ` Denis Kenzior
2023-10-16 20:20                 ` Simonas Kazlauskas
2023-10-21 23:23                   ` Simonas Kazlauskas
2023-10-22 20:14                     ` Denis Kenzior
2023-10-24 12:32                       ` James Prestwood [this message]
2023-10-24 14:26                         ` Denis Kenzior
2023-10-24 15:06                           ` James Prestwood
2023-10-24 15:32                             ` Denis Kenzior
2023-10-24 15:40                               ` James Prestwood
2023-10-24 15:19                           ` Simonas Kazlauskas
2023-10-24 15:29                             ` Denis Kenzior
2023-10-16 18:36           ` Denis Kenzior
2023-10-14 17:42   ` Simonas Kazlauskas

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=9e12bf94-aa83-4fe6-b045-8dab45b264ae@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=denkenz@gmail.com \
    --cc=iwd.lists.linux.dev@kazlauskas.me \
    --cc=iwd@lists.linux.dev \
    /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

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.