From: d@taht.net (Dave Täht)
To: Jonathan Morton <chromatix99@gmail.com>
Cc: grenville armitage <garmitage@swin.edu.au>,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Progress with latency-under-load tool
Date: Sun, 20 Mar 2011 16:47:16 -0600 [thread overview]
Message-ID: <87ei61e7ez.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <87k4fte83o.fsf@cruithne.co.teklibre.org> ("Dave =?utf-8?Q?T?= =?utf-8?Q?=C3=A4ht=22's?= message of "Sun, 20 Mar 2011 16:32:27 -0600")
d@taht.net (Dave Täht) writes:
> The interesting outlier thus far is 8... I'm tempted to stop the test
> now and recompile for testing 3 u/l 3 d/l first....
Scenario 12: 2 uploads, 2 downloads... 4725 KiB/s up, 3645 KiB/s down, 0.81 Hz smoothness
... Still running tests ...
> Txqueuelen = 1000 = ~1.5Mbyte (and I'm struggling with using consistent
> decimal or base 2 units this month) Mibibyte?
>
> Normal dma tx ring size ranges from 64 to 512, can be seen sometimes
> with ethtool -g device
With wireless you also have TX_RETRIES = 13 for these (ath9) devices
drivers under test. (Reduced to 4 in the less bloated version I can't
test right now)
You also have contention from other devices, and the occasional complete
retrain from a base figure of 1Mbit/sec up, while devices struggle to
regain sync.
There are (presumably helpful) effects of packet aggregation.
You also have modulo issues against the size of the tx queues, an
interaction with the network flow scheduler (what triggers filling the
tx queue?), SACK/DSACK and lost ACK retransmits, and probably more
issues than I've been able to come up with offhand.
--
Dave Taht
http://nex-6.taht.net
next prev parent reply other threads:[~2011-03-20 22:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0D59AD34-AA64-4376-BB8E-58C5D378F488@gmail.com>
[not found] ` <4D829B58.1070601@swin.edu.au>
2011-03-20 10:45 ` Jonathan Morton
[not found] ` <AANLkTin1UwEqDiBHvWQ7xi4jP0O4ifhsoBWnWJjE7Byv@mail.gmail.com>
2011-03-20 14:33 ` Fwd: " Pedro Tumusok
2011-03-20 14:42 ` Jonathan Morton
2011-03-20 20:33 ` grenville armitage
2011-03-20 20:53 ` Dave Täht
2011-03-20 21:52 ` Jonathan Morton
2011-03-20 22:32 ` Dave Täht
2011-03-20 22:47 ` Dave Täht [this message]
2011-03-20 22:52 ` Jonathan Morton
2011-03-20 22:55 ` Dave Täht
2011-03-20 23:42 ` Dave Täht
2011-03-20 21:50 ` Some results of the latency under load tool Dave Täht
2011-03-20 22:24 ` Jonathan Morton
[not found] ` <m3d3llgln8.fsf@yahoo.com>
2011-03-21 6:43 ` [Bloat] Progress with latency-under-load tool Jonathan Morton
2011-03-23 10:33 ` Otto Solares Cabrera
2011-03-23 11:26 ` Jonathan Morton
2011-03-23 19:27 ` Otto Solares
2011-03-23 20:40 ` Jonathan Morton
2011-03-23 22:32 ` Dave Hart
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=87ei61e7ez.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=garmitage@swin.edu.au \
/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