From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [RFC V3] bcm43xx-mac80211: Provide information to allow transmission rate decreases
Date: Thu, 02 Aug 2007 14:44:34 -0500 [thread overview]
Message-ID: <46B23422.3050207@lwfinger.net> (raw)
In-Reply-To: <200708021805.17004.mb@bu3sch.de>
Michael Buesch wrote:
> On Thursday 02 August 2007, Larry Finger wrote:
>> Michael,
>>
>> I couldn't find any long/short indication in the header, so I added a bool that
>> is set when the frame is sent.
>
> This is not going to work.
>
> But we can do this differently.
> You can do something like:
>
> if (!status->acked && !tx_control->noack)
> excessive_retries = 1;
>
> So we don't need to care about the retry count.
>
> Anyway. I don't know why we need excessive_retries _at_ _all_.
> The rc algorithm does already know if the frame succeed or failed
> anyway.
Is this what you had in mind?
Larry
@@ -1311,6 +1311,9 @@ void bcm43xx_dma_handle_txstatus(struct
*/
if (status->acked)
meta->txstat.flags |= IEEE80211_TX_STATUS_ACK;
+ else
+ if (!(meta->txstat.flags & IEEE80211_TXCTL_NO_ACK))
+ meta->txstat.excessive_retries = 1;
meta->txstat.retry_count = status->frame_count - 1;
ieee80211_tx_status_irqsafe(dev->wl->hw, meta->skb, &(meta->txstat));
/* skb is freed by ieee80211_tx_status_irqsafe() */
next prev parent reply other threads:[~2007-08-02 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 15:38 [RFC V3] bcm43xx-mac80211: Provide information to allow transmission rate decreases Larry Finger
2007-08-02 16:05 ` Michael Buesch
2007-08-02 16:33 ` Larry Finger
2007-08-02 19:44 ` Larry Finger [this message]
2007-08-02 19:59 ` Michael Buesch
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=46B23422.3050207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.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.