Netdev List
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: acme@redhat.com
Cc: dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: [DCCP] [PATCH 0/3]: Finishing Ack Vector patch set
Date: Tue,  8 Jan 2008 14:07:53 +0000	[thread overview]
Message-ID: <1199801276-16955-1-git-send-email-gerrit@erg.abdn.ac.uk> (raw)
In-Reply-To: finishing_ackvector_patch_set

This is the "new stuff" for Ack Vectors, completing the Ack Vector work.

All other patches are as before, with the single exception of the update sent
yesterday (the recovery strategy for dealing with suddenly large losses).

Arnaldo, can you please indicate whether I should resubmit the older patches.

After some more testing I am positive that these are now ready to be considered.

Patch #1: Addresses the pending FIXME, if Ack Vectors grow too large for a packet,
          their variable-length information is transported via a separate/scheduled
	  Sync. This mechanism can also be used for other out-of-band signalling
	  (e.g. slow-receiver option).

Patch #2: Since there is already a rich option-parsing infrastructure in options.c,
          it is not necessary to replicate the code to parse Ack Vectors. This patch
	  adds utility routines to store parsed Ack Vectors, which are processed by
	  the existing infrastructure via the hc_tx_parse_options() interface.

Patch #3: Integrates patch #3 for use with CCID2.	  

All patches have been uploaded to git://eden-feed.erg.abdn.ac.uk/dccp_exp

             reply	other threads:[~2008-01-08 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 14:07 Gerrit Renker [this message]
2008-01-08 14:07 ` [PATCH 1/3] [ACKVEC]: Schedule SyncAck when running out of space Gerrit Renker
2008-01-08 14:07   ` [PATCH 2/3] [ACKVEC]: Separate skb option parsing from CCID-specific code Gerrit Renker
2008-01-08 14:07     ` [PATCH 3/3] [CCID2]: Add option-parsing code to process Ack Vectors at the HC-sender Gerrit Renker

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=1199801276-16955-1-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