From: Nick Feamster <feamster@cc.gatech.edu>
To: d@taht.net (Dave Täht)
Cc: bismark-users@lists.bufferbloat.net
Subject: Re: [Bismark-users] coping with conflicts
Date: Tue, 15 Mar 2011 14:58:27 -0400 [thread overview]
Message-ID: <587F76A9-5EED-4D3D-B339-DE3979F50853@cc.gatech.edu> (raw)
In-Reply-To: <87tyf4fc42.fsf@cruithne.co.teklibre.org>
I think we are both interested in:
- measuring the current state of affairs (as a baseline)
- designing techniques to try to improve latencies/problems
- measuring how well respective techniques improve latencies/problems
On Mar 15, 2011, at 2:54 PM, Dave Täht wrote:
> Nick Feamster <feamster@cc.gatech.edu> writes:
>
>> I agree.
>
> To what? :)
>
> Would you consider your existing study "ground truth" and the upcoming
> one "revealed truth"?
>
> When I talked to de-heisenberging below, the goal would be to eliminate
> or at least compensate/understand the factors introduced by the
> measurement box.
>
> Measuring cable modem and DSL latencies/problems and the internet
> itself, remain a goal, but, for example, the end-user experience of
> using the box itself with some/much of the new stuff is important to
> us.
>
>>
>> On Mar 15, 2011, at 2:43 PM, Srikanth Sundaresan wrote:
>>
>>> It seems to me that they can coexist; to study the impact of the
>>> changes, we do need to know the existing ground truth, no?
>>>
>>> - Srikanth
>>>
>>> On 03/15/2011 02:42 PM, Dave Täht wrote:
>>>>
>>>>
>>>> I have some conflicts that I would like to clearly resolve as we ramp
>>>> up.
>>>>
>>>> 1) The bufferbloat project is trying to fix the internet
>>>> 2) you are trying to study the internet as it exists
>>>>
>>>> While some of the bufferbloat fixes in the pipeline will de-heisenberg your
>>>> measurements, the two ideas do conflict somewhat as does your schedule
>>>> vs ours.
>>>>
>>>> The wndr3700, which 6+ people have now, is looking to become a focus of
>>>> our efforts for item 1, and may ultimately become a model for the
>>>> "perfect router". (Although I would bet on the upcoming 32MB flash stuff
>>>> coming out later this year as a better model)
>>>>
>>> _______________________________________________
>>> Bismark-users mailing list
>>> Bismark-users@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bismark-users
>>
>> _______________________________________________
>> Bismark-users mailing list
>> Bismark-users@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bismark-users
>
> --
> Dave Taht
> http://nex-6.taht.net
next prev parent reply other threads:[~2011-03-15 18:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 18:42 Dave Täht
2011-03-15 18:43 ` Srikanth Sundaresan
2011-03-15 18:47 ` Nick Feamster
2011-03-15 18:54 ` Dave Täht
2011-03-15 18:58 ` Nick Feamster [this message]
2011-03-15 19:02 ` Dave Täht
2011-03-15 19:06 ` Nick Feamster
2011-03-15 19:19 ` Poole, Brian
2011-03-15 19:24 ` Nick Feamster
2011-03-15 19:31 ` Srikanth Sundaresan
2011-03-15 20:08 ` Nick Feamster
2011-03-16 8:37 ` Walter de Donato
2011-03-15 20:31 ` Dave Täht
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=587F76A9-5EED-4D3D-B339-DE3979F50853@cc.gatech.edu \
--to=feamster@cc.gatech.edu \
--cc=bismark-users@lists.bufferbloat.net \
--cc=d@taht.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