From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] A bit of history on RFC970 and RFC896 from john nagle
Date: Tue, 19 Apr 2016 19:03:38 +0200 [thread overview]
Message-ID: <878u098r9x.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw4sf1EAtUx4XriKkmwV9URgCwrR1ZSH5dAde=DqZLjfQQ@mail.gmail.com>
> The classic solution, from X.25, was an accumulation timer with a human
> response time sized delay. That's a bad idea, but unfortunately the
> people who put in delayed ACKs didn't know that. They were trying to
> fix TELNET responsiveness at Berkeley, which was using a large number of
> dumb terminals connected to terminal servers at the time. Delayed ACKs
> with a fixed timer are useful in that situation, and in few others.
Nagle has made this point repeatedly, and it's a convincing one. Is
anyone working on improving the delack algorithm?
> Bufferbloat is only bad if the queuing is FIFO-dumb. It's fine to have
> lots of queue space if you manage it well.
Noted.
-- Juliusz
prev parent reply other threads:[~2016-04-19 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 2:38 Dave Taht
2016-04-19 17:03 ` Juliusz Chroboczek [this message]
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=878u098r9x.wl-jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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