All of lore.kernel.org
 help / color / mirror / Atom feed
From: Burak Gorkemli <burakgmail-dccp@yahoo.com>
To: dccp@vger.kernel.org
Subject: Re: [Announce]: Test results with latest CCID3 patch set
Date: Thu, 13 Dec 2007 13:28:48 +0000	[thread overview]
Message-ID: <75619.32740.qm@web30008.mail.mud.yahoo.com> (raw)
In-Reply-To: <20071210154008.GA16839@gerrit.erg.abdn.ac.uk>

Gerrit,

I am cloning your tree with the following command:

    git-clone git://eden-feed.erg.abdn.ac.uk/dccp_exp my_dccp


But I did not check out the DCCP sub-branch, by:

    git-checkout --track -b dccp origin/dccp


However, as I type this command above, git complains saying:

    git checkout: branch dccp already exists


It this OK to say so?
 
--
Burak

----- Original Message ----
> 
> Burak
> 
> I have tried to replay your results but can not find anything
> wrong
> 
 with the current test kernel.
> Please have a look at the results below, I repeated the same
> experiment
> 
 on two different testbeds.
> 
> Incidentally, these results agree with the values you observed for
> TCP
> 
 Reno. It seems that the
> setup is not right, I am happy to help debugging this but I don't
> think
> 
 that there is a problem
> with the test kernel.
> 
> Can you please describe your setup - maybe something went wrong.
> 
> The first thing to check is whether you are really using the test
> tree
> 
 - it is necessary to check
> out the `dccp' subtree, if you are on the `master' instead of
> the
> 
 `dccp' subtree, then you are
> using a vanilla 2.6.24-rc5.  A detailed HowTo is on
>        
> 
 http://www.linux-foundation.org/en/Net:DCCP_Testing#Experimental_DCCP_source_tr
> ee
> The difference can also easily be told in the
> Request/Response
> 
 handshake, the CCIDs are now
> fully negotiated; the first value of the ConfirmL/R in
> the
> 
 DCCP-Response says which CCIDs are
> used (but they are still nonetheless set
> via
> 
 net.dccp.default.{rx,tx}_ccid).
> 

<snip>


  parent reply	other threads:[~2007-12-13 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 15:40 [Announce]: Test results with latest CCID3 patch set Gerrit Renker
2007-12-11 13:59 ` Alessio Botta
2007-12-11 14:21 ` Gerrit Renker
2007-12-11 17:40 ` Arnaldo Carvalho de Melo
2007-12-12 14:45 ` Burak Gorkemli
2007-12-12 16:42 ` Gerrit Renker
2007-12-12 20:40 ` Burak Gorkemli
2007-12-12 23:19 ` Alessio Botta
2007-12-12 23:21 ` Alessio Botta
2007-12-13  0:29 ` Arnaldo Carvalho de Melo
2007-12-13  9:37 ` Gerrit Renker
2007-12-13 13:28 ` Burak Gorkemli [this message]
2007-12-13 14:14 ` Gerrit Renker
2007-12-13 16:35 ` 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=75619.32740.qm@web30008.mail.mud.yahoo.com \
    --to=burakgmail-dccp@yahoo.com \
    --cc=dccp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.