From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: tcp wifi upload performance and lots of ACKs
Date: Mon, 4 Jun 2012 19:47:34 +0100 [thread overview]
Message-ID: <CAA93jw7ZRt+WfsKYw1SvJoq-bCGmvNjTK8FV_x5ZpzeSx_AbJA@mail.gmail.com> (raw)
In-Reply-To: <4FCCFE76.3060304@candelatech.com>
I was getting a bit more than this in the general case with the last
cut of cerowrt.
what are y'all getting with a good (300Mbit) link and various wifi cards?
---------- Forwarded message ----------
From: Ben Greear <greearb@candelatech.com>
Date: Mon, Jun 4, 2012 at 7:29 PM
Subject: tcp wifi upload performance and lots of ACKs
To: netdev <netdev@vger.kernel.org>
I'm going some TCP performance testing on wifi -> LAN interface
connections. With
UDP, we can get around 250Mbps of payload throughput. With TCP, max
is about 80Mbps.
I think the problem is that there are way too many ACK packets, and
bi-directional
traffic on wifi interfaces really slows things down. (About 7000 pkts
per second in
upload direction, 2000 pps download. And the vast majority of the download pkts
are 66 byte ACK pkts from what I can tell.)
Kernel is 3.3.7+
Anyone know of any tuning parameters that would let the receiving socket wait a
bit longer and send more ACK data in fewer packets?
Packet traces and other info available if anyone wants to take a look.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/
parent reply other threads:[~2012-06-04 18:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4FCCFE76.3060304@candelatech.com>]
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=CAA93jw7ZRt+WfsKYw1SvJoq-bCGmvNjTK8FV_x5ZpzeSx_AbJA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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