From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dpreed@reed.com
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] happy 4th!
Date: Tue, 9 Jul 2013 07:48:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1307090734420.8891@uplift.swm.pp.se> (raw)
In-Reply-To: <1373316621.879922633@apps.rackspace.com>
On Mon, 8 Jul 2013, dpreed@reed.com wrote:
> I was suggesting that there is no reason to be intimidated.
I was not intimidated, I just lacked data to actually reply to the
statement made.
> And yes, according to the dictionary definition, they are ignorant - as
> in they don't know what they are talking about, and don't care to.
I object to the last part of the statement. If you're a person who has
been involved in winning an Internet Land Speed Record you probably care,
but you're have knowledge for a certain application and a certain purpose,
which might not be applicable to the common type of home connection usage
today. It doesn't mean the use case is not important or that person is
opposing solving bufferbloat problem.
> As to being constructive, I'm not convinced that these people can be
> convinced that their dismissal of bufferbloat and their idea that
> "goodput" is a useful Internet concept are incorrect.
I haven't heard any dismissal of the problem, only that they optimize for
a different use case, and they're concerned that their use case will
suffer if buffers are smaller. This is the reason I want data because if
FQ_CODEL gets similar results then their use case is not hugely negatively
affected, and there is data showing it helps a lot for a lot of other use
cases, then they shouldn't have much to worry about and can stop arguing.
Thinking of Galileo, he didn't walk around saying "the earth revolves
around the sun" and when people questioned him, he said "check it out for
yourself, prove your point, I don't need to prove mine!", right?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-07-09 5:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 19:33 Dave Taht
2013-07-04 5:57 ` Mikael Abrahamsson
2013-07-04 13:51 ` Michael Richardson
2013-07-04 15:48 ` Mikael Abrahamsson
2013-07-07 18:52 ` dpreed
2013-07-08 0:24 ` Mikael Abrahamsson
2013-07-08 17:03 ` Toke Høiland-Jørgensen
2013-07-09 3:24 ` Dave Taht
2013-07-09 6:04 ` Mikael Abrahamsson
2013-07-09 6:32 ` Dave Taht
2013-07-09 7:30 ` [Cerowrt-devel] [Codel] " Andrew McGregor
2013-07-09 13:09 ` Eric Dumazet
2013-07-09 7:57 ` [Cerowrt-devel] " Toke Høiland-Jørgensen
2013-07-09 12:56 ` [Cerowrt-devel] [Codel] " Eric Dumazet
2013-07-09 13:13 ` Toke Høiland-Jørgensen
2013-07-09 13:23 ` Eric Dumazet
2013-07-09 13:25 ` Toke Høiland-Jørgensen
2013-07-09 13:36 ` Eric Dumazet
2013-07-09 13:45 ` Toke Høiland-Jørgensen
2013-07-09 13:49 ` Eric Dumazet
2013-07-09 13:53 ` Toke Høiland-Jørgensen
2013-07-09 14:07 ` Eric Dumazet
2013-07-08 20:50 ` [Cerowrt-devel] " dpreed
2013-07-08 21:04 ` Jim Gettys
2013-07-09 5:48 ` Mikael Abrahamsson [this message]
2013-07-09 5:58 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1307090734420.8891@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.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