From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 1/2] nl80211: add extended feature for BSS selection support
Date: Wed, 06 Jan 2016 15:36:38 +0100 [thread overview]
Message-ID: <1452090998.2541.18.camel@sipsolutions.net> (raw)
In-Reply-To: <568CE980.5050005@broadcom.com>
On Wed, 2016-01-06 at 11:16 +0100, Arend van Spriel wrote:
> So do we want want a dedicated "bss selection capability" flag iso
> extended feature in which the driver can indicate the supported
> selection criteria to user-space? Guess so.
Frankly, I'm not really quite sure.
The alternative is to just treat all of this as advisory and not worry,
so that userspace can specify all it wants and the driver will use all
it can.
That seems mostly reasonable as well.
> I played a trick in reusing ATTR_BSS_SELECT_BAND_PREF. When
> ATTR_BSS_SELECT_RSSI_ADJUST is passed the ATTR_BSS_SELECT_BAND_PREF
> is
> used to determine in which band the rssi is adjusted. So "band" and
> "rssi_adjust" are mutual exclusive.
Yeah, OK, I think that might have confused me a bit :)
> > But logically - does it even make sense? If you already prefer that
> > band, why give it a boost still? Just disable RSSI? Hmm.
>
> I hope the use-cases mentioned clarify this.
>
Right. So realistically, writing this a bit more verbosely, you have
1) rssi_preference, band_preference(band)
2) rssi_adjust(band, delta), rssi_preference
and perhaps
3) rssi_preference
as the default?
As for 1), you said it was "band, rssi" but it seems you really meant
the other way around since before you said "band" was a tie-breaker.
Perhaps then, the API should just expose the two "primitives"
* band_preference(band)
* rssi_adjust(band, delta)?
johannes
next prev parent reply other threads:[~2016-01-06 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 12:19 [RFC 0/2] nl80211: allow configuration of BSS selection Arend van Spriel
2015-12-24 12:19 ` [RFC 1/2] nl80211: add extended feature for BSS selection support Arend van Spriel
2016-01-05 9:25 ` Johannes Berg
2016-01-05 9:50 ` Arend van Spriel
2016-01-05 16:31 ` Johannes Berg
2016-01-06 10:16 ` Arend van Spriel
2016-01-06 14:36 ` Johannes Berg [this message]
2016-01-06 14:37 ` Johannes Berg
2016-01-07 12:52 ` Arend van Spriel
2016-01-07 14:41 ` Johannes Berg
2016-01-08 9:18 ` Arend van Spriel
2015-12-24 12:19 ` [RFC 2/2] brcmfmac: add support for nl80211 BSS_SELECT feature Arend van Spriel
2015-12-25 10:08 ` [RFC 0/2] nl80211: allow configuration of BSS selection Arend van Spriel
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=1452090998.2541.18.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.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).