From: Kalle Valo <kalle.valo@nokia.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
Ron Rindjunsky <ron.rindjunsky@intel.com>
Subject: Re: cfg80211 API changes
Date: Mon, 04 Feb 2008 07:52:44 +0200 [thread overview]
Message-ID: <87ve55b74j.fsf@nokia.com> (raw)
In-Reply-To: <1ba2fa240802030651x58ab6c63yd1b4d9ccaa2ecd42@mail.gmail.com> (ext Tomas Winkler's message of "Sun\, 3 Feb 2008 16\:51\:27 +0200")
Tomas Winkler <tomasw@gmail.com> writes:
>> TBH, that confused me completely since the rate scale algorithm tells
>> the hardware what rate to use so why does the hw need to assign a
>> different rate in the tx status?
>
> I see. Rate scale algorithm only tels FW from what rate to start
> transmission. FW is responsible to do downscaling. Which is quite
> reasonable as retransmission is real time process. Instead of
> retransmitting on the same rate FW downscales. T X response provides
> to the rate scaling algorithm the successful rate.
I just want to point out this is an important feature when the bus is
very slow, for example SPI bus in embedded devices. Retransfering
frames through SPI for every rate restransmit would make such a device
extremely slow.
--
Kalle Valo
next prev parent reply other threads:[~2008-02-04 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ba2fa240802030539h132c7365g1bc1c20b1c560c0@mail.gmail.com>
2008-02-03 13:55 ` cfg80211 API changes Tomas Winkler
2008-02-03 14:37 ` Johannes Berg
2008-02-03 14:51 ` Tomas Winkler
2008-02-04 5:52 ` Kalle Valo [this message]
2008-02-04 17:19 ` Sam Leffler
2008-02-04 18:20 ` Kalle Valo
2008-02-04 20:01 ` Tomas Winkler
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=87ve55b74j.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ron.rindjunsky@intel.com \
--cc=tomasw@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 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.