Netdev List
 help / color / mirror / Atom feed
From: rhee@ncsu.edu
To: "Douglas Leith" <doug@eee.strath.ac.uk>
Cc: netdev@vger.kernel.org, end2end-interest@postel.org
Subject: Re: FW: Performance evaluation of high speed TCPs
Date: Fri, 3 Feb 2006 15:17:39 -0500 (EST)	[thread overview]
Message-ID: <58352.61.86.155.104.1138997859.squirrel@webmail.ncsu.edu> (raw)
In-Reply-To: <C0FF12BB5B83E44ABAEAA47149DA97350FE0F6@helios.eee.strath.ac.uk>

Let's get off this e2e list for this discussion. It is really unnecessary
to use this list for
this discussion. I don't understand why you keep sending your email to
this list even
though we are seating next to each other in the same conference. Isn't
this amusing
 or abusing of this mailing list? :-)
-- 
to others in the list, Doug and I are attending pfldnet in japan now..




> Injong,
>
>>In fact, i contacted your student "Baruch" one month and half before  we
>> posted our
> report -- it was CCed in the netdev mailing list as well and we gave him
> login and
> passwd on our result website (at that time we were just about to write the
> report)
> and we have not heard from your guys until just one week ago. At least we
> did try to
> make sure we are running a buggy version.
>
> We have no record of receiving such an email.  Just a mix-up I guess.
>
> Doug
>
>
>>>Seriously, we can't run the tests for every fix and bug report.
>>
>> Perhaps best to view it as returning a favour.  You may recall that we
>> re-ran all our own experimental tests last year (all data and code
>> available online at www.hamilton.ie/net/eval/) on discovering a
>> previously
>> unreported bug introduced by the linux folks when implementing bic.
>> Something similar has happened with importing htcp into linux.
>>
>> Seriously, where's the value in comparing buggy implementations - isn't
>> that just a waste of all our time ?  If we are genuine about wanting to
>> understand tcp performance then I think we just have to take the hit
>> from
>> issues such as this that are outside all of our control.
>>
>> Doug
>>
>> Hamilton Institute
>> www.hamilton.ie
>>
>
>
>
>

  reply	other threads:[~2006-02-03 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C0FF12BB5B83E44ABAEAA47149DA973508266A@helios.eee.strath.ac.uk>
     [not found] ` <C0FF12BB5B83E44ABAEAA47149DA973508266D@helios.eee.strath.ac.uk>
     [not found]   ` <39307.60.44.142.168.1138932213.squirrel@webmail.ncsu.edu>
2006-02-03  2:24     ` FW: Performance evaluation of high speed TCPs Douglas Leith
2006-02-03  2:50       ` rhee
2006-02-03 14:06         ` Douglas Leith
2006-02-03 20:17           ` rhee [this message]
2006-02-03  2:51       ` 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=58352.61.86.155.104.1138997859.squirrel@webmail.ncsu.edu \
    --to=rhee@ncsu.edu \
    --cc=doug@eee.strath.ac.uk \
    --cc=end2end-interest@postel.org \
    --cc=netdev@vger.kernel.org \
    /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