From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat at LUG talk - Meeting Report
Date: Wed, 19 Dec 2012 13:05:30 +0100 [thread overview]
Message-ID: <50D1AD8A.1020907@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <E6E1E816-457E-41E0-9A36-C0BD3AFBD265@pnsol.com>
> Every TCP transfer (which may be collection of web page accesses) that reaches an instantaneous packet rate in-excess of the capacity of the most constrained network element on the path causes such problems.
Which problems? I'm missing the relation to my original post.
Oliver
next prev parent reply other threads:[~2012-12-19 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4092.1353748990.1742.cerowrt-devel@lists.bufferbloat.net>
[not found] ` <A2E41EFF-2507-457D-9086-06E718192D22@intermapper.com>
2012-12-09 16:56 ` Richard Brown
2012-12-09 17:32 ` [Bloat] [Cerowrt-devel] " Maciej Soltysiak
2012-12-10 0:16 ` Richard Brown
2012-12-12 14:26 ` [Bloat] " Oliver Hohlfeld
2012-12-19 10:21 ` Neil Davies
2012-12-19 12:05 ` Oliver Hohlfeld [this message]
2012-12-19 12:20 ` Jonathan Morton
2012-12-19 12:44 ` Oliver Hohlfeld
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D1AD8A.1020907@net.t-labs.tu-berlin.de \
--to=oliver@net.t-labs.tu-berlin.de \
--cc=bloat@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