From: Kalle Valo <kvalo@codeaurora.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>,
Enrico Mioso <mrkiko.rs@gmail.com>,
Daniel Golle <daniel@makrotopia.org>,
Felix Fietkau <nbd@nbd.name>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [1/2] rt2x00: pause almost full queue early
Date: Mon, 8 Jan 2018 17:40:17 +0000 (UTC) [thread overview]
Message-ID: <20180108174017.A371C60818@smtp.codeaurora.org> (raw)
In-Reply-To: <1513683236-13402-1-git-send-email-sgruszka@redhat.com>
Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> Do not drop &queue->tx_lock and acquire it again to pause queue when
> available entries are below the threshold.
>
> Patch should mitigate problem of frequently printed errors:
> "Error - Dropping frame due to full tx queue"
>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> Tested-by: Enrico Mioso@gmail.com
> Tested-by: Enrico Mioso <mrkiko.rs@gmail.com>
2 patches applied to wireless-drivers-next.git, thanks.
3d8f162cb8ec rt2x00: pause almost full queue early
6dd80efd75ce rt2x00: do not pause queue unconditionally on error path
--
https://patchwork.kernel.org/patch/10123101/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-01-08 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 11:33 [PATCH 1/2] rt2x00: pause almost full queue early Stanislaw Gruszka
2017-12-19 11:33 ` [PATCH 2/2] rt2x00: do not pause queue unconditionally on error path Stanislaw Gruszka
2017-12-26 11:02 ` Enrico Mioso
2017-12-26 11:01 ` [PATCH 1/2] rt2x00: pause almost full queue early Enrico Mioso
2017-12-26 11:02 ` Enrico Mioso
2018-01-08 17:40 ` Kalle Valo [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180108174017.A371C60818@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=daniel@makrotopia.org \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mrkiko.rs@gmail.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.com \
/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.