From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: TCP TSQ regression affecting ath10k throughput
Date: Wed, 13 Nov 2013 13:12:15 +0200 [thread overview]
Message-ID: <87ob5o7dyo.fsf@kamboji.qca.qualcomm.com> (raw)
Hi,
Sujith reported a regression in TCP which caused a major decrease in
ath9k and ath10k throughput:
http://thread.gmane.org/gmane.linux.network/290269
The commit which broke this is c9eeec26e32e ("tcp: TSQ can use a dynamic
limit") and this patch seems to fix it:
http://patchwork.ozlabs.org/patch/290672/
I have cherry picked the fix to ath.git master branch to make it easier
for ath10k developers.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: TCP TSQ regression affecting ath10k throughput
Date: Wed, 13 Nov 2013 13:12:15 +0200 [thread overview]
Message-ID: <87ob5o7dyo.fsf@kamboji.qca.qualcomm.com> (raw)
Hi,
Sujith reported a regression in TCP which caused a major decrease in
ath9k and ath10k throughput:
http://thread.gmane.org/gmane.linux.network/290269
The commit which broke this is c9eeec26e32e ("tcp: TSQ can use a dynamic
limit") and this patch seems to fix it:
http://patchwork.ozlabs.org/patch/290672/
I have cherry picked the fix to ath.git master branch to make it easier
for ath10k developers.
--
Kalle Valo
next reply other threads:[~2013-11-13 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 11:12 Kalle Valo [this message]
2013-11-13 11:12 ` TCP TSQ regression affecting ath10k throughput Kalle Valo
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=87ob5o7dyo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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 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.