linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
	linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 1/2] cfg80211: add a field for the bitrate of the last rx data packet from a station
Date: Tue, 15 Feb 2011 09:55:06 +0100	[thread overview]
Message-ID: <1297760106.3935.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTi=wkmAeBKXv8PKhVRJXFdY_NO7jS+vwFJueuBpL@mail.gmail.com>

On Mon, 2011-02-14 at 23:08 -0800, Luis R. Rodriguez wrote:
> On Mon, Feb 14, 2011 at 2:06 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2011-02-10 at 16:29 +0100, Felix Fietkau wrote:
> >> Also fix a typo in the STATION_INFO_TX_BITRATE description
> >>
> >> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> >> ---
> >>  include/linux/nl80211.h |    3 ++
> >>  include/net/cfg80211.h  |    5 +++-
> >>  net/wireless/nl80211.c  |   56 +++++++++++++++++++++++++++++++----------------
> >>  3 files changed, 44 insertions(+), 20 deletions(-)
> >>
> >> diff --git a/include/linux/nl80211.h b/include/linux/nl80211.h
> >> index 821ffb9..35bfec2 100644
> >> --- a/include/linux/nl80211.h
> >> +++ b/include/linux/nl80211.h
> >> @@ -1243,6 +1243,8 @@ enum nl80211_rate_info {
> >>   * @NL80211_STA_INFO_LLID: the station's mesh LLID
> >>   * @NL80211_STA_INFO_PLID: the station's mesh PLID
> >>   * @NL80211_STA_INFO_PLINK_STATE: peer link state for the station
> >> + * @NL80211_STA_INFO_RX_BITRATE: last unicast rx rate, nested attribute
> >> + *   containing info as possible, see &enum nl80211_sta_info_txrate.
> >
> > I think it would make sense to restrict this to data frames, as mgmt
> > frames will often be sent with a low rate.
> 
> Would it be useful to show both? How about per AC?

Why would anyone care about mgmt frames unless they're debugging
something (in which case I recommend monitor interface)? And normally
rate control shouldn't care about the AC so that seems pointless?

johannes


  reply	other threads:[~2011-02-15  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 15:29 [PATCH 1/2] cfg80211: add a field for the bitrate of the last rx data packet from a station Felix Fietkau
2011-02-10 15:29 ` [PATCH 2/2] mac80211: add support for showing the last rx bitrate Felix Fietkau
2011-02-14 10:07   ` Johannes Berg
2011-02-14 10:06 ` [PATCH 1/2] cfg80211: add a field for the bitrate of the last rx data packet from a station Johannes Berg
2011-02-15  7:08   ` Luis R. Rodriguez
2011-02-15  8:55     ` Johannes Berg [this message]
2011-02-15 21:57       ` Luis R. Rodriguez

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=1297760106.3935.0.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=nbd@openwrt.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).