From: Justin McCann <jneilm@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] The challenge
Date: Thu, 10 May 2012 10:25:10 -0400 [thread overview]
Message-ID: <CAFkTFa_SwgnWURKH8XL=_TW24jCegHDToT6jgHAcS-zivZDJ-g@mail.gmail.com> (raw)
In-Reply-To: <1336633359.27520.147.camel@shinybook.infradead.org>
On Thu, May 10, 2012 at 3:02 AM, David Woodhouse <dwmw2@infradead.org> wrote:
>
> If we overload the DSLAM, it drops one ATM cell out of N, which nixes
> fairly much *every* IP packet by dropping a tiny part of each one, and
> results in almost zero throughput. We don't let the DSLAM do
> buffering :)
<tangent>
Can't they turn on Early Packet Discard or something similar? This
seems like a no-brainer.
Dynamics of TCP Traffic over ATM Networks (1994), Allyn Romanow , Sally Floyd
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.30.7647
"We investigate the performance of TCP connections over ATM networks
without ATM-level congestion control, and compare it to the
performance of TCP over packet-based networks. For simulations of
congested networks, the effective throughput of TCP over ATM can be
quite low when cells are dropped at the congested ATM switch. The low
throughput is due to wasted bandwidth as the congested link transmits
cells from `corrupted' packets, i.e., packets in which at least one
cell is dropped by the switch. We investigate two packet discard
strategies which alleviate the effects of fragmentation. Partial
Packet Discard, in which remaining cells are discarded after one cell
has been dropped from a packet, somewhat improves throughput. We
introduce Early Packet Discard, a strategy in which the switch drops
whole packets prior to buffer overflow. This mechanism prevents
fragmentation and restores throughput to maximal levels."
</tangent>
next prev parent reply other threads:[~2012-05-10 14:25 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 1:04 [Codel] " Dave Taht
2012-05-09 2:02 ` [Codel] [Bloat] " Kevin Gross
2012-05-09 3:13 ` [Codel] " Kathleen Nichols
2012-05-09 3:56 ` Dave Taht
2012-05-09 5:16 ` [Codel] [Bloat] " Simon Barber
2012-05-09 5:40 ` Eric Dumazet
2012-05-09 5:41 ` Dave Taht
2012-05-09 7:32 ` [Codel] [codel] some numbers on dual 10Gb links Eric Dumazet
2012-05-09 13:04 ` [Codel] [Bloat] The challenge Kevin Gross
2012-05-16 5:55 ` Jonathan Morton
2012-05-16 6:09 ` Eric Dumazet
2012-05-16 7:05 ` [Codel] Exploring the potential of codel, fq_codel, and qfq dave taht
2012-05-16 7:20 ` Dave Taht
2012-05-16 7:42 ` [Codel] [Bloat] " Eric Dumazet
2012-05-16 7:46 ` Eric Dumazet
2012-05-16 8:17 ` Eric Dumazet
2012-05-16 9:02 ` Jonathan Morton
2012-05-16 9:14 ` Eric Dumazet
2012-05-16 9:31 ` Jonathan Morton
2012-05-16 9:37 ` Eric Dumazet
2012-05-16 9:59 ` Jonathan Morton
2012-05-16 10:10 ` Eric Dumazet
2012-05-16 13:58 ` Eric Dumazet
2012-05-16 17:40 ` Rick Jones
2012-05-16 17:53 ` Eric Dumazet
2012-05-16 17:33 ` [Codel] " Rick Jones
2012-05-16 17:48 ` [Codel] [Bloat] " Eric Dumazet
2012-05-16 6:09 ` [Codel] [Bloat] The challenge Dave Taht
2012-05-16 6:31 ` Eric Dumazet
2012-05-16 8:15 ` Jonathan Morton
2012-05-09 19:10 ` Roger Jørgensen
2012-05-09 19:15 ` Dave Taht
2012-05-09 19:28 ` Dave Taht
2012-05-09 20:02 ` Simon Barber
2012-05-09 20:06 ` Fred Baker
2012-05-09 21:47 ` Jim Gettys
2012-05-09 23:58 ` Eric Dumazet
2012-05-10 2:34 ` Jonathan Morton
2012-05-10 2:37 ` Dave Taht
2012-05-10 6:35 ` David Woodhouse
2012-05-10 6:54 ` Jonathan Morton
2012-05-10 7:02 ` David Woodhouse
2012-05-10 14:25 ` Justin McCann [this message]
2012-05-10 14:42 ` David Woodhouse
2012-05-10 15:34 ` Neil Davies
2012-05-10 21:20 ` Jim Gettys
2012-05-14 7:27 ` Jonathan Morton
2012-05-14 7:34 ` Eric Dumazet
2012-05-14 13:55 ` David Woodhouse
2012-05-18 20:56 ` [Codel] [Bloat] Linux-able modems Jonathan Morton
2012-05-18 21:36 ` Dave Taht
2012-05-18 22:34 ` Dave Taht
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFkTFa_SwgnWURKH8XL=_TW24jCegHDToT6jgHAcS-zivZDJ-g@mail.gmail.com' \
--to=jneilm@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dwmw2@infradead.org \
/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