From: "Injong Rhee" <rhee@eos.ncsu.edu>
To: <l.andrew@ieee.org>, <rhee@ncsu.edu>
Cc: "Douglas Leith" <doug.leith@nuim.ie>, <netdev@vger.kernel.org>,
<floyd@icsi.berkeley.edu>, <lisongxu@gmail.com>,
<end2end-interest@postel.org>
Subject: Re: [e2e] performance of BIC-TCP, High-Speed-TCP, H-TCP etc
Date: Thu, 28 Sep 2006 12:33:32 -0400 [thread overview]
Message-ID: <00c401c6e31b$d75c9970$4a580e98@ncsu2cc0c3fa00> (raw)
In-Reply-To: aa7d2c6d0609271620h74a5cffxae22fd46daaa3f29@mail.gmail.com
Sure. I don't mind doing this test. I am currently working with Doug Leith
to get to the bottom of this difference. So when we get to the PFLDnet, we
should have some more findings on this. But I am up for this challenge.
----- Original Message -----
From: "Lachlan Andrew" <lachlan.andrew@gmail.com>
To: <rhee@ncsu.edu>
Cc: "Douglas Leith" <doug.leith@nuim.ie>; <netdev@vger.kernel.org>;
<floyd@icsi.berkeley.edu>; <lisongxu@gmail.com>; "Injong Rhee"
<rhee@eos.ncsu.edu>; <end2end-interest@postel.org>
Sent: Wednesday, September 27, 2006 7:20 PM
Subject: Re: [e2e] performance of BIC-TCP, High-Speed-TCP, H-TCP etc
> Greetings all,
>
> On 23/09/06, rhee@ncsu.edu <rhee@ncsu.edu> wrote:
>> Just i was pondering why we got different results and try to see if we
>> can
>> come to some understanding on this different results we got. Who knows we
>> together might run into some fundamental research issues regarding
>> testing.
>
> Since many interested parties will be around LA for PFLDnet, how about
> getting together after that (Friday 9 Feb) to re-run some of the
> disputed tests on one set of hardware, with everyone present to debate
> the results?
>
> You're all welcome to come to Caltech to do the testing. We can
> provide a few servers, dummynets and Gigabit switches. Everyone is
> welcome to bring their scripts, and any other hardware they need.
>
> If there is interest, we could also have things like a round-table
> discussion of the benefits of testing with different file-length
> distributions (like long lived flows to understand what is happening
> vs a range of flows to test suitability for deployment), and the
> benefits of repeating other people's tests vs testing in as many
> scenarios as possible.
>
> Who is interested in coming?
>
> Cheers,
> Lachlan
>
> --
> Lachlan Andrew Dept of Computer Science, Caltech
> 1200 E California Blvd, Mail Code 256-80, Pasadena CA 91125, USA
> Phone: +1 (626) 395-8820 Fax: +1 (626) 568-3603
>
next prev parent reply other threads:[~2006-09-28 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 2:34 performance of BIC-TCP, High-Speed-TCP, H-TCP etc Injong Rhee
2006-09-23 6:34 ` [e2e] " Douglas Leith
2006-09-23 7:45 ` rhee
2006-09-23 9:43 ` Douglas Leith
2006-09-27 23:20 ` Lachlan Andrew
2006-09-28 16:33 ` Injong Rhee [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-23 2:43 Injong Rhee
2006-09-24 4:18 ` Stephen Hemminger
2006-09-24 4:25 ` Stephen Hemminger
[not found] <4513F1A1.3000506@nuim.ie>
2006-09-22 17:42 ` Ian McDonald
2006-09-22 19:38 ` Douglas Leith
2006-09-22 20:04 ` Ian McDonald
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='00c401c6e31b$d75c9970$4a580e98@ncsu2cc0c3fa00' \
--to=rhee@eos.ncsu.edu \
--cc=doug.leith@nuim.ie \
--cc=end2end-interest@postel.org \
--cc=floyd@icsi.berkeley.edu \
--cc=l.andrew@ieee.org \
--cc=lisongxu@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rhee@ncsu.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