From: Dave Taht <d@taht.net>
To: bismark-users@lists.bufferbloat.net
Subject: [Bismark-users] issues with slow-start.
Date: Wed, 06 Apr 2011 06:02:04 -0600 [thread overview]
Message-ID: <4D9C563C.4030206@taht.net> (raw)
The traces I took (of connecting to youtube) during yesterday's meeting
at gatech were interesting.
Most of the problems with dropped packets, and reordering, I saw,
appeared to occur during slow start!?!??
Here's an example:
http://www.teklibre.com/~d/captures/earlytrace.png
WTF?
My thought is that there is either something wrong with my box, or the
shapers you are using, or the wireless interface(s) I was connected to.
Usually what I see is chaos AFTER a few seconds, not during slow start.
(It's an otherwise normal tcp trace after it ramps up)
I'd like to re-run those tests using a few different interfaces and
laptops to gain more insight into the problem.
Also somewhat related to this is if that if any other group(s) want some
insight into the bufferbloat issue, I'm here, I have jg's slides, I can
talk to it for an hour...
And similarly having at least one representative from the other group we
met with yesterday on this list and the website would be good.
reply other threads:[~2011-04-06 12:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D9C563C.4030206@taht.net \
--to=d@taht.net \
--cc=bismark-users@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