DCCP protocol discussions
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: [PATCH 0/3]: The last three
Date: Mon, 18 Jun 2007 14:40:30 +0000	[thread overview]
Message-ID: <200706181540.30737@strip-the-willow> (raw)

These three patches finally complete the set. Yes, it's done.


Patch #1: Makes CCID3 feedback explicit (initial | periodic | parameter-change)
          and makes the estimate of X_recv more reliable in the following combined
          case: (a) loss has occurred already; (b) periodic feedback has been sent.
          In this case, the previously computed value for X_recv is reused (from
          the last periodic feedback), since it has been computed over a longer time
          (one RTT or more); whereas in contrast the time between current feedback
          and the instant of the last periodic feedback is smaller - and hence X_recv
          less accurate.

Patch #2: Removes redundant variable for `p': we use `pinv' exclusively in the CCID3 
          code, and updating both p and pinv for each incoming packet is very expensive.


Patch #3: Update copyrights of CCID3/TFRC files. This has been diffed and `updated'
          with regards to the recent changes in Arnaldos tree.
          

Note: As of now, the whole patch set is available within the experimental test tree, 
      as sub-branch `dccp' on  	git://eden-feed.erg.abdn.ac.uk/dccp_exp

      Detailed instructions how to pull the tree will follow in separate email.
      Patches on this tree will be updated with regard to results of discussions
      on this list, so please test, comment, and contribute.
     
      If you have a recent davem-2.6 tree, you can pull the sub-tree by

        1. checking out a branch `dccp':         git checkout -b dccp master
	2. pulling the subtree into this branch: 
                 git pull git://eden-feed.erg.abdn.ac.uk/dccp_exp.git dccp
           
         

                 reply	other threads:[~2007-06-18 14:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200706181540.30737@strip-the-willow \
    --to=gerrit@erg.abdn.ac.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox