Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: cerowrt@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bug #442] < vs <= in two comparisons
Date: Sat, 19 Apr 2014 11:00:39 -0700	[thread overview]
Message-ID: <CAA93jw6woReS_JwjLhDpn9Dbaty2PxXF6b5uqzUZxayFeQd6Mw@mail.gmail.com> (raw)
In-Reply-To: <53525C84.8030809@openwrt.org>

On Sat, Apr 19, 2014 at 4:22 AM, Felix Fietkau <nbd@openwrt.org> wrote:
> On 2014-04-19 05:26, Dave Taht wrote:
>> Could part of it be as simple as not checking for '<='  but only < in
>> txq_max_pending below?
> I don't see how that would make any meaningful difference in practice.

Didn't think it would, still thought <= was more correct.

> By the way, did you test my patch?

It is in the as yet untested 3.10.36-6 build, along with resetting qlen
down to 12 again to try to trigger the bug sooner.

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.36-6/


>
>> in ath_tx_start:
>>
>>         ath_txq_lock(sc, txq);
>>         if (txq == sc->tx.txq_map[q] &&
>>             ++txq->pending_frames > sc->tx.txq_max_pending[q] &&
>>             !txq->stopped) {
>>                 ieee80211_stop_queue(sc->hw, q);
>>                 txq->stopped = true;
>>         }
>>
>> in ath_txq_skb_done:
>>
>>         if (txq->stopped &&
>>             txq->pending_frames < sc->tx.txq_max_pending[q]) {
>>                 ieee80211_wake_queue(sc->hw, q);
>>                 txq->stopped = false;
>>         }
>>
>>
>



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

      reply	other threads:[~2014-04-19 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19  3:26 Dave Taht
2014-04-19 11:22 ` Felix Fietkau
2014-04-19 18:00   ` Dave Taht [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6woReS_JwjLhDpn9Dbaty2PxXF6b5uqzUZxayFeQd6Mw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt@lists.bufferbloat.net \
    --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