1. 04 9月, 2008 1 次提交
    • G
      dccp: Set per-connection CCIDs via socket options · fade756f
      Gerrit Renker 提交于
      With this patch, TX/RX CCIDs can now be changed on a per-connection basis, which
      overrides the defaults set by the global sysctl variables for TX/RX CCIDs.
      
      To make full use of this facility, the remaining patches of this patch set are
      needed, which track dependencies and activate negotiated feature values.
      
      Note on the maximum number of CCIDs that can be registered:
      -----------------------------------------------------------
      The maximum number of CCIDs that can be registered on the socket is constrained
      by the space in a Confirm/Change feature negotiation option. 
      
      The space in these in turn depends on the size of header options as defined
      in RFC 4340, 5.8. Since this is a recurring constant, it has been moved from
      ackvec.h into linux/dccp.h, clarifying its purpose.
      
      Relative to this size, the maximum number of CCID identifiers that can be 
      present in a Confirm option (which always consumes 1 byte more than a Change
      option, cf. 6.1) is 2 bytes less than the maximum TLV size: one for the
      CCID-feature-type and one for the selected value.
      Signed-off-by: NGerrit Renker <gerrit@erg.abdn.ac.uk>
      fade756f
  2. 29 1月, 2008 1 次提交
  3. 21 12月, 2007 1 次提交
  4. 11 10月, 2007 1 次提交
  5. 03 12月, 2006 2 次提交
  6. 25 10月, 2006 1 次提交
  7. 23 9月, 2006 1 次提交
  8. 01 7月, 2006 1 次提交
  9. 21 3月, 2006 3 次提交
  10. 04 1月, 2006 1 次提交
  11. 09 10月, 2005 1 次提交
  12. 18 9月, 2005 1 次提交