From: Srikanth Sundaresan <srikanth@gatech.edu>
To: "Poole, Brian" <bpoole@cc.gatech.edu>
Cc: "bismark-devel@lists.bufferbloat.net"
<bismark-devel@lists.bufferbloat.net>
Subject: Re: [Bismark-devel] bismark-active
Date: Tue, 26 Apr 2011 17:21:16 -0400 [thread overview]
Message-ID: <4DB7374C.80302@gatech.edu> (raw)
In-Reply-To: <FC2117C703F33143ACE5AAD34CF98FBC1489406E@aeatlgtrmbx01.gtri.ext>
I think eventually we will go with that. The only thing I don't like
about that is it's hard to remember whose is which. :)
On 04/26/2011 05:18 PM, Poole, Brian wrote:
> We can add auto-device naming if we decide on the convention to use. I had the MAC address (based on eth0) one mocked up before. Shall we just go with that? <whatever-the-prefix-was><full-mac-address-minus-the-colons> ?
>
> Brian
> ________________________________________
> From: bismark-devel-bounces@lists.bufferbloat.net [bismark-devel-bounces@lists.bufferbloat.net] on behalf of Srikanth Sundaresan [srikanth@gatech.edu]
> Sent: Tuesday, April 26, 2011 5:16 PM
> To: bismark-devel@lists.bufferbloat.net
> Subject: [Bismark-devel] bismark-active
>
> bismark-mgmt seems to work. It needs some more testing, and there's also
> a manual component (naming the device), but it seems to be in good shape.
>
> To start testing bismark-active, we need the following scripts:
>
> bismark-measure-active
> bismark-tr
> bismark-rtr
> bismark-ping
> bismark-netperf
> bismark-netperf-thread
> bismark-dns
> bismark-ditg
> bismark-sp
>
> The binaries:
> shaperprobe
> ITGRecv
> ITGSend
> ITGDec
>
> packages:
> gnu-time
> bind-host
> curl(preferable, but not necessary)
>
> - Srikanth
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
next prev parent reply other threads:[~2011-04-26 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:16 Srikanth Sundaresan
2011-04-26 21:18 ` Poole, Brian
2011-04-26 21:21 ` Srikanth Sundaresan [this message]
2011-04-26 21:22 ` Dave Taht
2011-04-27 10:26 ` Walter de Donato
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=4DB7374C.80302@gatech.edu \
--to=srikanth@gatech.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=bpoole@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