From: Johannes Berg <johannes@sipsolutions.net>
To: Timo Lindhorst <tlnd@online.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] mac80211_hwsim: Report rate info in tx status
Date: Wed, 28 Mar 2012 11:32:30 +0200 [thread overview]
Message-ID: <1332927150.3479.25.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201203281128.27956.tlnd@online.de>
On Wed, 2012-03-28 at 11:28 +0200, Timo Lindhorst wrote:
> Hey,
>
> > + if (!ack)
> > + for (i = 0; i < IEEE80211_TX_MAX_RATES; i++)
> > + tx_count[i] = txi->control.rates[i].count;
> > +
> > ieee80211_tx_info_clear_status(txi);
> > if (!(txi->flags & IEEE80211_TX_CTL_NO_ACK) && ack)
> > txi->flags |= IEEE80211_TX_STAT_ACK;
> > +
> > + if (ack) {
> > + txi->status.rates[0].count = 1;
> > + txi->status.rates[1].idx = -1;
> > + } else {
> > + for (i = 0; i < IEEE80211_TX_MAX_RATES; i++)
> > + txi->control.rates[i].count = tx_count[i];
> > + }
> > +
> > ieee80211_tx_status_irqsafe(hw, skb);
> > }
>
> I know: backing up the count values, clearing the status, and restoring the
> values if necessary is kind of ugly. Would it be better to partly clear the
> status manually instead of using ieee80211_tx_info_clear_status() ?
Yeah just noticed the ieee80211_tx_info_clear_status() in there too...
OTOH, what are you using this for? It seems almost like we should always
just set
txi->status.rates[0].count = 1;
since we never attempted multiple transmits? I'm not really sure though,
it's a corner case ... I could also imagine this being populated by
userspace (wmediumd) but I guess that isn't there now ...
johannes
next prev parent reply other threads:[~2012-03-28 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:17 [PATCH] mac80211_hwsim: Report rate info in tx status Timo Lindhorst
2012-03-28 9:28 ` Johannes Berg
2012-03-28 9:28 ` Timo Lindhorst
2012-03-28 9:32 ` Johannes Berg [this message]
2012-03-28 13:47 ` Timo Lindhorst
2012-04-30 18:34 ` John W. Linville
2012-05-03 19:33 ` Johannes Berg
2012-05-03 21:34 ` Javier Cardona
2012-05-07 23:17 ` Javier Cardona
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=1332927150.3479.25.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tlnd@online.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.