public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Jouni Malinen <j@w1.fi>, Tomas Winkler <tomas.winkler@intel.com>,
	Vasanthakumar Thiagarajan <vasanth@atheros.com>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: rate control vs. bands
Date: Thu, 02 Oct 2008 10:40:45 +0200	[thread overview]
Message-ID: <1222936845.24551.34.camel@johannes.berg> (raw)
In-Reply-To: <1221223890.11204.33.camel@johannes.berg> (sfid-20080912_145214_760432_1456136F)

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]


> During my rate control work I noticed that the band handling there is
> somewhat awkward, and I wanted to collect opinions.
> 
> Currently, much of the code assumes that neither we nor station in our
> bSS change bands; the PID algorithm even says:
> 
>         /* We can safely assume that sband won't change unless we get
>          * reinitialized. */
> 
> which doesn't really seem true.

I haven't checked so far, but I think you can make it switch:
 * bring up two IBSS interfaces in 2.4 GHz, have them sync
 * switch the leader to a channel in 5 GHz
 * the follower will hopefully find the leader and switch there, but the
   sta_info for the follower will, on the leader, still have sband 2GHz

> For the rate control algorithms, I was just thinking about removing the
> rate_init() callback because this can just as well be done when
> allocating the station. However, currently we don't pass the band to the
> alloc_sta function, so that isn't possible right now.

So it seems that this sucks for rate control algorithms; we need to make
sure rate_init is always called during alloc_sta initially (so we don't
forget like mesh does right now! nbd, make sure to test mesh and
possibly fix it please.)

We also need to investigate calling rate_init again when the sta has
switched band for some reason.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2008-10-02  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 12:51 rate control vs. bands Johannes Berg
2008-09-12 13:09 ` Johannes Berg
2008-10-02  8:40 ` Johannes Berg [this message]

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=1222936845.24551.34.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=tomas.winkler@intel.com \
    --cc=vasanth@atheros.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