From: Johannes Berg <johannes@sipsolutions.net>
To: Antonio Quartulli <antonio@open-mesh.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] cfg80211: add get_max_tp() API
Date: Fri, 05 Apr 2013 15:20:01 +0200 [thread overview]
Message-ID: <1365168001.8515.28.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130405083956.GA14463@open-mesh.com>
On Fri, 2013-04-05 at 10:39 +0200, Antonio Quartulli wrote:
> In the batman-adv module (which implements a routing protocol for mesh networks
> on layer 2) we are trying to switch metric from packet loss to throughput and
> the idea is to read the estimation from the rate control component (thanks to
> the API mechanism in cfg/mac80211 this can be eventually changed later).
While this makes some sense, going into the details of your patchset I
find that it's overly complex.
I think you should fix minstrel to report the best rate in
txrc.reported_rate. This would also have the effect of not showing
sampling attempts to userspace in the "current TX rate", which generally
makes a lot of sense.
After doing that, reading the rate becomes a get_station_info() call or
so.
One more detail:
int cfg80211_get_max_tp(struct wireless_dev *wdev, u8 *peer, u32 *tp)
I really don't think that the wireless_dev should be necessary for this,
it ought to be just a netdev IMHO. Also, the peer should be const :)
johannes
next prev parent reply other threads:[~2013-04-05 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 19:57 [PATCH 1/3] cfg80211: add get_max_tp() API Antonio Quartulli
2013-04-04 19:57 ` [PATCH 2/3] mac80211: add rate_control_ops::get_max_tp() and implement it Antonio Quartulli
2013-04-04 19:57 ` [PATCH 3/3] mac80211: implement cfg80211_ops::get_max_tp() API Antonio Quartulli
2013-04-05 8:21 ` [PATCH 1/3] cfg80211: add get_max_tp() API Helmut Schaa
2013-04-05 8:39 ` Antonio Quartulli
2013-04-05 13:20 ` Johannes Berg [this message]
2013-04-06 7:33 ` Antonio Quartulli
2013-04-09 10:25 ` Johannes Berg
2013-04-09 11:34 ` Antonio Quartulli
2013-04-11 9:56 ` Johannes Berg
2013-04-11 9:57 ` Johannes Berg
2013-04-12 14:10 ` Antonio Quartulli
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=1365168001.8515.28.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=antonio@open-mesh.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).