From: Dave Taht <dave.taht@gmail.com>
To: Nick Feamster <feamster@cc.gatech.edu>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] about ready to do another build
Date: Fri, 20 May 2011 16:15:13 -0600 [thread overview]
Message-ID: <BANLkTindJ5fB1TOMC3NtuvvDygyxMoJ3Vw@mail.gmail.com> (raw)
In-Reply-To: <5C1FCBFC-B007-4B01-A7BA-6CCD5523DC34@cc.gatech.edu>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Fri, May 20, 2011 at 4:12 PM, Nick Feamster <feamster@cc.gatech.edu>wrote:
> Srikanth, Walter --- please chime in.
>
> Dave has a point here about the possibility of stopping QoS during testing.
>
> Thoughts?
>
Well, actually, doing this this way, would get some GREAT data from the
field that simply doesn't exist right now...
/etc/init.d/qos stop
do the test (which I assume includes shaperprobe and a bandwidth test)
/etc/init.d/qos start
do the bandwidth test
I've also been collecting data via usb sticks on these puppies. For slow
connections (less than 2MB/sec) the writes to stick and the dump do not seem
to permute the results much.
>
> -Nick
>
>
> On May 21, 2011, at 12:11 AM, Dave Taht wrote:
>
> > And your customer experience will be poor, and you will be measuring
> tcp/ip malfunctioning rather than working properly.
> >
> > How hard would it be for your scripts, when doing bandwidth testing, to
> do a
> >
> > /etc/init.d/qos stop
> > do the test
> > /etc/init.d/qos start
> >
> > When do they do bandwidth testing? What script does it?
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1869 bytes --]
next prev parent reply other threads:[~2011-05-20 22:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 20:27 Dave Taht
2011-05-20 21:40 ` Nick Feamster
2011-05-20 21:41 ` Nick Feamster
2011-05-20 22:11 ` Dave Taht
2011-05-20 22:12 ` Nick Feamster
2011-05-20 22:15 ` Dave Taht [this message]
2011-05-20 22:16 ` Nick Feamster
2011-05-20 22:28 ` Dave Taht
2011-05-20 22:35 ` Nick Feamster
2011-05-20 22:42 ` Dave Taht
2011-05-20 22:47 ` Dave Taht
2011-05-20 23:22 ` Nick Feamster
2011-05-20 23:27 ` Dave Taht
2011-05-20 23:29 ` Nick Feamster
2011-05-20 23:27 ` Nick Feamster
2011-05-21 8:12 ` Srikanth Sundaresan
2011-05-21 12:09 ` Nick Feamster
[not found] ` <BANLkTikzEnRk8D0D4yR-4smqPiMYW0OH4A@mail.gmail.com>
2011-05-21 15:48 ` Srikanth Sundaresan
2011-05-21 16:08 ` Dave Taht
2011-05-21 16:33 ` Srikanth Sundaresan
2011-05-21 16:49 ` Dave Taht
2011-05-21 16:53 ` Nick Feamster
2011-05-21 17:07 ` Srikanth Sundaresan
2011-05-23 13:20 ` Jim Gettys
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=BANLkTindJ5fB1TOMC3NtuvvDygyxMoJ3Vw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=feamster@cc.gatech.edu \
/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