Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Felix Fietkau <nbd@openwrt.org>, Chr <chunkeey@web.de>
Subject: Re: [RFT] p54: implement MRR
Date: Sun, 12 Oct 2008 02:06:27 +0200	[thread overview]
Message-ID: <1223769987.3581.11.camel@johannes.berg> (raw)
In-Reply-To: <1223769491.3581.8.camel@johannes.berg> (sfid-20081012_015818_541064_B75F451C)

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

On Sun, 2008-10-12 at 01:58 +0200, Johannes Berg wrote:

> +	/*
> +	 * We support at most 8 tries no matter which rate they're at,
> +	 * we cannot support max_rates * max_rate_tries as we set it
> +	 * here, but setting it correctly to 4/2 or so would limit us
> +	 * artificially if the RC algorithm wants just two rates, so
> +	 * let's say the max of rates and three tries each, and clip
> +	 * it to a total of 8.
> +	 */
> +	dev->max_rates = IEEE80211_TX_MAX_RATES;
> +	dev->max_rate_tries = 3;

Ideally, of course, we'd set max_rates to 8 and max_rate_tries to 1, but
we don't have enough space for that in the tx info (no 8 rates
possible). Hence, the next best thing that matches the HW well would be
4/2 and have the rate control algorithms program the same rate more than
once if it wants more than two tries. Same in mac80211. Thoughts? Is
that feasible?

johannes

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

      reply	other threads:[~2008-10-12  0:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 23:56 [RFT] mac80211/drivers: rewrite the rate control API Johannes Berg
2008-10-11 13:16 ` Johannes Berg
2008-10-11 23:55 ` [RFT v2] " Johannes Berg
2008-10-11 23:58   ` [RFT] p54: implement MRR Johannes Berg
2008-10-12  0:06     ` 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=1223769987.3581.11.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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