linux-toradex.git/net/dccp/ccids, branch v2.6.33.1

dccp ccid-3: Remove CCID naming redundancy 2/2

2009-10-07T20:51:24+00:00

This continues the previous patch, by applying the same change to CCID-3.

Signed-off-by: Gerrit Renker 
Acked-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

dccp ccid-2: Remove CCID naming redundancy 1/2

2009-10-07T20:51:23+00:00

This removes a redundancy in the CCID half-connection (hc) naming scheme:
 * instead of 'hctx->tx_...', write 'hc->tx_...';
 * instead of 'hcrx->rx_...', write 'hc->rx_...';

which works because the 'type' of the half-connection is encoded in the
'rx_' / 'tx_' prefixes.

Signed-off-by: Gerrit Renker 
Acked-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

dccp ccid-3: Overhaul CCID naming convention 2/2

2009-10-07T20:51:22+00:00

This implements the new naming scheme also for CCID-3.

Signed-off-by: Gerrit Renker 
Acked-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

dccp ccid-2: Overhaul CCID naming convention 1/2

2009-10-07T20:51:21+00:00

This patch starts a less problematic naming convention for CCID structs.

The old naming convention used 'hc{tx,rx}->ccid?hc{tx,rx}->...' as
recurring prefixes, which made the code
 * hard to write (not easy to fit into 80 characters);
 * hard to read  (most of the space is occupied by prefixes).

The new naming scheme:
 * struct entries for the TX socket are prefixed by 'tx_';
 * and those for the RX socket are prefixed by 'rx_'.

The identifiers then remain distinguishable when grep-ing through the tree:
 (a) RX/TX sockets are distinguished by the naming scheme,
 (b) individual CCIDs are distinguished by filename (ccid{2,3,4}.{c,h}).

This first patch implements the scheme for CCID-2.

Signed-off-by: Gerrit Renker 
Acked-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

net-next-2.6 [PATCH 1/1] dccp: ccids whitespace-cleanup / CodingStyle

2009-09-15T00:02:54+00:00

No code change, cosmetical changes only:

 * whitespace cleanup via scripts/cleanfile,
 * remove self-references to filename at top of files,
 * fix coding style (extraneous brackets),
 * fix documentation style (kernel-doc-nano-HOWTO).

Thanks are due to Ivo Augusto Calado who raised these issues by
submitting good-quality patches.

Signed-off-by: Gerrit Renker 
Signed-off-by: David S. Miller

net: mark read-only arrays as const

2009-08-05T17:42:58+00:00

String literals are constant, and usually, we can also tag the array
of pointers const too, moving it to the .rodata section.

Signed-off-by: Jan Engelhardt 
Signed-off-by: David S. Miller

dccp ccid-3: Fix RFC reference

2009-01-11T08:17:22+00:00

Thanks to Wei and Arnaldo for pointing out the correct
new reference for CCID-3.

Signed-off-by: Gerrit Renker 
Signed-off-by: David S. Miller

net: fix section mismatch warnings in dccp/ccids/lib/tfrc.c

2009-01-11T08:11:28+00:00

Removed the __exit annotation of tfrc_lib_exit(), in order to suppress the following section mismatch messages:

WARNING: net/dccp/dccp.o(.text+0xd9): Section mismatch in reference from the function ccid_cleanup_builtins() to the function .exit.text:tfrc_lib_exit()
The function ccid_cleanup_builtins() references a function in an exit section.
Often the function tfrc_lib_exit() has valid usage outside the exit section
and the fix is to remove the __exit annotation of tfrc_lib_exit.

WARNING: net/dccp/dccp.o(.init.text+0x48): Section mismatch in reference from the function ccid_initialize_builtins() to the function .exit.text:tfrc_lib_exit()
The function __init ccid_initialize_builtins() references
a function __exit tfrc_lib_exit().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
tfrc_lib_exit() so it may be used outside an exit section.

Signed-off-by: Leonardo Potenza 
Acked-by: Arnaldo Carvalho de Melo 
Acked-by: Gerrit Renker 
Signed-off-by: David S. Miller

dccp: Integrate the TFRC library with DCCP

2009-01-05T05:45:33+00:00

This patch integrates the TFRC library, which is a dependency of CCID-3 (and
CCID-4), with the new use of CCIDs in the DCCP module.		

Signed-off-by: Gerrit Renker 
Signed-off-by: David S. Miller

dccp: Lockless integration of CCID congestion-control plugins

2009-01-05T05:42:53+00:00

Based on Arnaldo's earlier patch, this patch integrates the standardised
CCID congestion control plugins (CCID-2 and CCID-3) of DCCP with dccp.ko:

 * enables a faster connection path by eliminating the need to always go 
   through the CCID registration lock;

 * updates the implementation to use only a single array whose size equals
   the number of configured CCIDs instead of the maximum (256);

 * since the CCIDs are now fixed array elements, synchronization is no
   longer needed, simplifying use and implementation.

CCID-2 is suggested as minimum for a basic DCCP implementation (RFC 4340, 10);
CCID-3 is a standards-track CCID supported by RFC 4342 and RFC 5348.

Signed-off-by: Gerrit Renker 
Signed-off-by: David S. Miller