From: Rafael Laufer <rlaufer@cs.ucla.edu>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Implementation of the IEEE80211_RADIOTAP_RATE option
Date: Fri, 21 Aug 2009 12:06:25 -0700 [thread overview]
Message-ID: <4A8EF031.4050604@cs.ucla.edu> (raw)
In-Reply-To: <69e28c910908211152k4423d098i92b25078139ee827@mail.gmail.com>
Gábor Stefanik wrote:
> 2009/8/21 Rafael Laufer <rlaufer@cs.ucla.edu>:
>
>> Gábor Stefanik wrote:
>>
>>> Maybe a new IEEE80211_TX_CTL_ or IEEE80211_TX_RC_ flag will also be
>>> needed, so Radiotap can indicate whether rate_control_get_rate needs
>>> to be called.
>>>
>> ok, I am resending the patch. I included a new flag called
>> IEEE80211_TX_CTL_RATE_RADIOTAP to indicate if the rate has
>> been set in the radiotap header. If not, then the rate control
>> algorithm is called.
>>
>
> Isn't it easier to check whether we already have a rate configured?
> (info->control.rates[0].idx is set to an invalid value before the
> rate_control_get_rate call AFAIK, unless you set it in the radiotap
> decoding function before.)
>
I guess it is also possible, but in that case you rely on the assumption
that the rate is invalid before rate_control_get_rate(). If in the
future this assumption does not hold, the code will break. If, however,
this is always gonna be true, I can change the code to use your
suggestion. Personally, I prefer to use another flag so that future
changes do not affect this code, but let me know what is best.
Rafael
next prev parent reply other threads:[~2009-08-21 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 0:40 [PATCH] Implementation of the IEEE80211_RADIOTAP_RATE option Rafael Laufer
2009-08-21 8:18 ` Johannes Berg
2009-08-21 13:30 ` Gábor Stefanik
2009-08-21 18:03 ` Rafael Laufer
2009-08-21 18:52 ` Gábor Stefanik
2009-08-21 19:06 ` Rafael Laufer [this message]
2009-08-21 19:57 ` Gábor Stefanik
2009-08-21 20:21 ` Rafael Laufer
2009-08-21 20:24 ` Rafael Laufer
2009-08-22 7:50 ` Johannes Berg
2009-08-22 22:05 ` Rafael Laufer
2009-08-22 7:48 ` Johannes Berg
2009-08-22 22:03 ` Rafael Laufer
2009-08-23 8:06 ` Kalle Valo
2009-08-23 9:11 ` Johannes Berg
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=4A8EF031.4050604@cs.ucla.edu \
--to=rlaufer@cs.ucla.edu \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@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).