DCCP protocol discussions
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: [PATCH 0/5]: Misc CCID3 patches | TFRC separate module | end of first half
Date: Thu, 14 Jun 2007 09:04:34 +0000	[thread overview]
Message-ID: <200706141004.34231@strip-the-willow> (raw)

This patch bundle completes the `first round' of the patch set. 

I have put in some work to make it compileable - there is
just one patch interdepence with regard to line 961 - the 
receiver RTT sampling, which is part of the second half of the
patch set.

However, for best results I do recommend applying all patches.

Patch submission will continue with the second half tomorrow; 
this has 21 patches,  so that the `end' can be expected by mid next week.

Comments will be addressed, and if there are no major disagreements,
I'd suggest to place the set into the test tree and make it available 
for pulling - in that way the changes are much easier to see.


Patch #1: CCID3 receiver does not set CCVal - fixed hereby.

Patch #2: Avoids double access of TX history when sending CCID3 feedback,
          removes an unused state and redundant variables in send_feedback(),
          and converts it to use the newer ktime_t interface.
          => This resolves one more dependency in the upgrade to ktime_t.        

Patch #3: Gathers repeated use of test-for-NULL statement into function call.

Patch #4: Update for the wait_for_ccid code (small optimisation)

Patch #5: Creates a central module source file, dccp/ccids/lib/tfrc_module.c,
          as a main file for dccp_tfrc_lib. Previously the module has been 
          assembled from packet_history.c, loss_interval.c, and tfrc_equation.c.
          Since each of these source files serves a distinct purpose, it was
          not clear where module initialisation, cleanup, and module parameters
          are to be stored - done now in this file. Plus a separate tfrc debug macro.

                 reply	other threads:[~2007-06-14  9:04 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=200706141004.34231@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