linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Ron Rindjunsky <ron.rindjunsky@intel.com>,
	linville@tuxdriver.com, johannes@sipsolutions.net
Subject: Re: [RFC v2] mac80211: add general rate information to Tx status
Date: Tue, 05 Feb 2008 23:18:53 +0100	[thread overview]
Message-ID: <47A8E0CD.5080202@openwrt.org> (raw)
In-Reply-To: <1ba2fa240802051140j6497593cq3776c77b75ee32be@mail.gmail.com>

Tomas Winkler wrote:
> On Feb 5, 2008 5:45 PM, Tomas Winkler <tomas.winkler@intel.com> wrote:
>> From: Ron Rindjunsky <ron.rindjunsky@intel.com>
>>
>> This patch introduces data structures meant to contain actual
>> configuration in which Tx was made in HW, for general purposes
>> and for rate scaling in specific.
>> it includes the rate, general flags for the rate (e.g. Tx antenna)
>> and the number of retries for the rate.
>>
>> Signed-off-by: Ron Rindjunsky <ron.rindjunsky@intel.com>
>> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
>> ---
>>  include/net/mac80211.h |   22 +++++++++++++++++++++-
>>  1 files changed, 21 insertions(+), 1 deletions(-)
>>
>> diff --git a/include/net/mac80211.h b/include/net/mac80211.h
>> index 460da54..ec966c8 100644
>> --- a/include/net/mac80211.h
>> +++ b/include/net/mac80211.h
>> @@ -318,6 +318,22 @@ struct ieee80211_rx_status {
>>  };
>>
>>  /**
>> + * struct ieee80211_tx_rate_ctrl - rate ctrl data
>> + *
>> + * The low-level driver should provide this struct as part
>> + * of the ieee80211_tx_status. this struct should give information
>> + * about the tx that is not part of the plcp rates table.
>> + * @bitrate: rate used.
>> + * @flags: Tx information (e.g. antenna selectd, guard interval, etc.)
>> + * @retry_count: number of retries for this specific rate
>> + */
>> +struct ieee80211_tx_rate_ctrl {
>> +       u32 bitrate;
>> +       u32 flags;
>> +       u8 retry_count;
>> +};
>> +
>> +/**
>>   * enum ieee80211_tx_status_flags - transmit status flags
>>   *
>>   * Status flags to indicate various transmit conditions.
>> @@ -343,7 +359,7 @@ enum ieee80211_tx_status_flags {
>>   * @control: a copy of the &struct ieee80211_tx_control passed to the driver
>>   *     in the tx() callback.
>>   * @flags: transmit status flags, defined above
>> - * @retry_count: number of retries
>> + * @retry_count: total number of retries
>>   * @excessive_retries: set to 1 if the frame was retried many times
>>   *     but not acknowledged
>>   * @ampdu_ack_len: number of aggregated frames.
>> @@ -353,6 +369,8 @@ enum ieee80211_tx_status_flags {
>>   * @ack_signal: signal strength of the ACK frame
>>   * @queue_length: ?? REMOVE
>>   * @queue_number: ?? REMOVE
>> + * @rate_ctrl_num: number of rate_ctrl allocated
>> + * @rate_ctrl: info for rate at which the packet was actually transmitted
>>   */
>>  struct ieee80211_tx_status {
>>         struct ieee80211_tx_control control;
>> @@ -364,6 +382,8 @@ struct ieee80211_tx_status {
>>         int ack_signal;
>>         int queue_length;
>>         int queue_number;
>> +       size_t rate_ctrl_num;
>> +       struct ieee80211_tx_rate_ctrl rate_ctrl[0];
>>  };
>>
>>  /**
>> --
>> 1.5.2.2
> 
> 
> Felix will this work for you?
Yes, looks good.

- Felix

  reply	other threads:[~2008-02-05 22:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 15:45 [RFC v2] mac80211: add general rate information to Tx status Tomas Winkler
2008-02-05 19:40 ` Tomas Winkler
2008-02-05 22:18   ` Felix Fietkau [this message]
2008-02-06 14:15 ` Johannes Berg
2008-02-06 14:44   ` Tomas Winkler
2008-02-06 14:58     ` Johannes Berg
2008-02-06 16:18       ` Tomas Winkler
2008-02-06 16:28         ` Johannes Berg
2008-02-06 18:04           ` Tomas Winkler
2008-02-07 10:41             ` Johannes Berg
2008-02-07 16:06               ` Nick Kossifidis

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