A small self-contained patch set which centers around determining sufficient 
headroom when calculating the maximum packet size.

Patch #1: Adds documentation for the fields in struct ccid_operations.

Patch #2: More informative registration of CCIDs.

Patch #3: Introduces the CCMPS field for CCIDs. This is currently only used
          by CCID4. The ccmps value needs to include network/transport header
          lengths (since dccp_sync_mss subtracts these). For CCID4 this would
          supposedly look like (RFC 3714/4828):
          struct ccid_operations ccid4 = {
                .ccid_mps = 1500,
                /* ... */
          If the field is omitted or set to 0, no CCMPS is imposed.

Patch #4: Is the core of this patch set and estimates the minimally required 
          headroom for Data/DataAck packets. It addresses a FIXME in 
          I have long thought about this and come to the conclusion that a 
          solution - optimising for data transfer - is better. The complexities 
          variable-length options (Ack Vector, Data Dropped, initial 
          need to use a different path - e.g. using a separate Ack (cf. next 
          Rationale and background is documented on 

Patch #5: Reorders statements to estimate the maximum room left for Ack Vectors 
and adds a Fixme + warning
          message for dealing with insufficient remaining space when 
piggybacking on DataAck.
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to