linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomasw@gmail.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: add rate to ieee80211_tx_status
Date: Mon, 04 Feb 2008 14:53:19 +0100	[thread overview]
Message-ID: <47A718CF.50303@openwrt.org> (raw)
In-Reply-To: <49711.::ffff:91.5.56.63.1202126931.squirrel@secure.sipsolutions.net>

Johannes Berg wrote:
> I thought we just agreed not to because they're not bit rate but rather
> rate control specific. Think of it this way: the rate control algorithm
> selects a bitrate and those control flags you mentioned (SISO/MIMO/...),
> right?
> 
> So the rate control algorithm has to communicate the bitrate and the flags
> to the hardware. It currently communicates the bitrate selection by giving
> a bitrate structure pointer (it could simply give the bitrate in kbps or
> whatever but that would mean the driver needs to look up its hw_value so
> this is the reason for passing the pointer) and cannot currently
> communicate the control flags selection.
> 
> So the way I see it we'd add something like "u32 rate_control_flags" to
> struct tx_control for the flags you wanted, and also add a similar field
> (to be able to reuse the flag definitions) to the tx status & rx status
> structs. It seems to me that makes most sense, no?
I'd like to have multiple rates in the tx status, including the number of
attempts for each rate. The Minstrel rate control needs these to build its
statistics properly.

- Felix

  parent reply	other threads:[~2008-02-04 14:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 20:15 [RFC] mac80211: add rate to ieee80211_tx_status Tomas Winkler
2008-02-04  8:46 ` Johannes Berg
2008-02-04  9:53   ` Tomas Winkler
     [not found]     ` <6231174111099834440@unknownmsgid>
2008-02-04 10:27       ` Tomas Winkler
     [not found]         ` <-6799378017406559341@unknownmsgid>
2008-02-04 11:05           ` Tomas Winkler
     [not found]             ` <-4694429725714512287@unknownmsgid>
2008-02-04 11:21               ` Tomas Winkler
     [not found]                 ` <-2417195033053015320@unknownmsgid>
2008-02-04 11:26                   ` Tomas Winkler
2008-02-04 11:30                     ` Tomas Winkler
     [not found]                       ` <5358276387473684738@unknownmsgid>
2008-02-04 11:57                         ` Tomas Winkler
     [not found]                           ` <5605009721259660313@unknownmsgid>
2008-02-04 13:35                             ` Tomas Winkler
     [not found]                           ` <49711.::ffff:91.5.56.63.1202126931.squirrel@secure.sipsolutions.net>
2008-02-04 13:53                             ` Felix Fietkau [this message]
     [not found]                               ` <-5971017268625562167@unknownmsgid>
2008-02-04 14:21                                 ` Tomas Winkler
     [not found]                                   ` <-7767648866191425885@unknownmsgid>
2008-02-04 15:13                                     ` Tomas Winkler
2008-02-04 15:24                                       ` Felix Fietkau
2008-02-04 18:36                                         ` Tomas Winkler
2008-02-04 18:39                                           ` Felix Fietkau
2008-02-04 19:03                                             ` Tomas Winkler
2008-02-04 19:05                                               ` Tomas Winkler
2008-02-05 21:23                                                 ` Stefano Brivio
2008-02-05 23:15                                                   ` Tomas Winkler
2008-02-06 14:13                                                     ` Johannes Berg
2008-02-04 19:07                                               ` Felix Fietkau

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=47A718CF.50303@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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).