From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: acme@redhat.com
Cc: dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH 0/8] [DCCP]: Updates and fixes to ensure code works with recent changes
Date: Sat, 8 Dec 2007 10:06:20 +0000 [thread overview]
Message-ID: <11971083882331-git-send-email-gerrit@erg.abdn.ac.uk> (raw)
Some of the recent changes in 2.6.25 cause problems with the existing implementation (i.e. break
the code). This patch set therefore provides fixes and resubmits one subsequent patch which
has not been considered so far, but which is part of the tfrc_lib package.
Patch #1: Performs whitespace cleanups.
Patch #2: Migrates all loss interval / packet history initialisation code into tfrc.c.
Patch #3: Removes two unused functions/function calls that have become obsolete now.
Patch #4: Splits rx_hist_add_packet() into its original constituents -- they are needed.
Patch #5: Restores the parts of the macro/inline conversion that broke the algorithm.
Patch #6: Is a v2 patch - the Loss Intervals code, now updated to work with the recent changes.
Patch #7: Reverts hiding inlines which are needed by the calling CCID module.
Patch #8: Also a patch v2 - shows how all the new stuff is integrated to work with CCID3.
The code compiles cleanly, all patches have been uploaded to the test tree (backported from 2.6.25),
git://eden-feed.erg.abdn.ac.uk/dccp_exp [dccp]
So far only a few quick bandwidth tests have been performed. These merely confirm that the stack
does not crash. Since most of this patch set deals with loss detection and re-ordering, some more
detailed tests are needed to ensure that the code, as before, deals well with loss, reordering,
and duplication (this requires at least one NetEm box).
Updates to the CCID4 subtree need to be suspended for a few days. There are too many fiddly changes
all over the place; until we understand exactly what is going on and if there has been a
regression, it is not a good idea to track everything.
next reply other threads:[~2007-12-08 10:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 10:06 Gerrit Renker [this message]
2007-12-08 10:06 ` [PATCH 1/8] [TFRC]: Whitespace cleanups Gerrit Renker
2007-12-08 10:06 ` [PATCH 2/8] [TFRC]: Put RX/TX initialisation into tfrc.c Gerrit Renker
2007-12-08 10:06 ` [PATCH 3/8] [TFRC/CCID3]: Remove now unused functions / function calls Gerrit Renker
2007-12-08 10:06 ` [PATCH 4/8] [TFRC]: Need separate entry_from_skb routine Gerrit Renker
2007-12-08 10:06 ` [PATCH 5/8] [TFRC]: Loss interval code needs the macros/inlines that were moved Gerrit Renker
2007-12-08 10:06 ` [PATCH 6/8] [PATCH v2] [TFRC]: Ringbuffer to track loss interval history Gerrit Renker
2007-12-08 10:06 ` [PATCH 7/8] [TFRC]: CCID3 (and CCID4) needs to access these inlines Gerrit Renker
2007-12-08 10:06 ` [PATCH 8/8] [PATCH v2] [CCID3]: Interface CCID3 code with newer Loss Intervals Database Gerrit Renker
2007-12-10 21:04 ` Arnaldo Carvalho de Melo
2007-12-11 9:42 ` Gerrit Renker
2007-12-11 17:22 ` Arnaldo Carvalho de Melo
2007-12-12 16:56 ` Gerrit Renker
2007-12-12 17:05 ` Arnaldo Carvalho de Melo
2007-12-12 17:21 ` Gerrit Renker
2007-12-08 18:47 ` [PATCH 5/8] [TFRC]: Loss interval code needs the macros/inlines that were moved Arnaldo Carvalho de Melo
2007-12-10 11:31 ` Gerrit Renker
2007-12-10 11:48 ` Arnaldo Carvalho de Melo
2007-12-08 17:16 ` [PATCH 3/8] [TFRC/CCID3]: Remove now unused functions / function calls Arnaldo Carvalho de Melo
2007-12-08 17:13 ` [PATCH 2/8] [TFRC]: Put RX/TX initialisation into tfrc.c Arnaldo Carvalho de Melo
2007-12-10 10:56 ` Gerrit Renker
2007-12-08 17:08 ` [PATCH 1/8] [TFRC]: Whitespace cleanups Arnaldo Carvalho de Melo
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=11971083882331-git-send-email-gerrit@erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=acme@redhat.com \
--cc=dccp@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).