From: Ryan Hsu <ryanhsu@codeaurora.org>
To: "Jonathan Morton" <chromatix99@gmail.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [Make-wifi-fast] [PATCH] mac80211: Adjust TSQ pacing shift
Date: Thu, 1 Mar 2018 17:09:47 -0800 [thread overview]
Message-ID: <cf67c430-d1e7-ef40-5c43-5f9557876fd8@codeaurora.org> (raw)
In-Reply-To: <AF418EFD-681C-4845-A114-23F54F100A9D@gmail.com>
On 02/14/2018 12:23 AM, Jonathan Morton wrote:
>> On 14 Feb, 2018, at 10:18 am, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> Why does the CPU usage go up >7?
> Just as a guess, it's generating extra packets which are then laboriously discarded and retransmitted.
>
> - Jonathan Morton
I think for 11n, like ath9k, it might be good enough for 8, but for 11ac could
aggregate a little more.
Yes, and CPU usage goes up after 6 or 7, might due to it generates extra
packets but the physical bus is capping the throughput, so that we can't see
much throughput difference after (or maybe my setup is not optimal, assumed we
should be seeing around 550-600Mbps for TCP in 11ac), but only the CPU usage
increased.
--
Ryan Hsu
prev parent reply other threads:[~2018-03-02 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:11 Toke Høiland-Jørgensen
2018-02-02 16:55 ` dpreed
2018-02-02 20:13 ` Arend van Spriel
2018-02-14 0:43 ` Ryan Hsu
2018-02-14 8:18 ` Toke Høiland-Jørgensen
2018-02-14 8:23 ` Jonathan Morton
2018-03-02 1:09 ` Ryan Hsu [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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf67c430-d1e7-ef40-5c43-5f9557876fd8@codeaurora.org \
--to=ryanhsu@codeaurora.org \
--cc=chromatix99@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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