|author||Gerrit Renker <firstname.lastname@example.org>||2007-10-04 14:50:57 -0700|
|committer||David S. Miller <email@example.com>||2007-10-10 16:54:37 -0700|
|parent||[DCCP]: Wrong format in printk (diff)|
[DCCP]: Correct documentation
This corrects erroneous documentation of the socket API. Signed-off-by: Gerrit Renker <firstname.lastname@example.org> Signed-off-by: Ian McDonald <email@example.com> Signed-off-by: Arnaldo Carvalho de Melo <firstname.lastname@example.org> Signed-off-by: David S. Miller <email@example.com>
Diffstat (limited to 'Documentation')
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/networking/dccp.txt b/Documentation/networking/dccp.txt
index fc8b4fa0b141..afb66f9a8aff 100644
@@ -55,12 +55,13 @@ be enabled at the receiver, too with suitable choice of CsCov.
DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
range 0..15 are acceptable. The default setting is 0 (full coverage),
values between 1..15 indicate partial coverage.
-DCCP_SOCKOPT_SEND_CSCOV is for the receiver and has a different meaning: it
+DCCP_SOCKOPT_RECV_CSCOV is for the receiver and has a different meaning: it
sets a threshold, where again values 0..15 are acceptable. The default
of 0 means that all packets with a partial coverage will be discarded.
Values in the range 1..15 indicate that packets with minimally such a
coverage value are also acceptable. The higher the number, the more
- restrictive this setting (see [RFC 4340, sec. 9.2.1]).
+ restrictive this setting (see [RFC 4340, sec. 9.2.1]). Partial coverage
+ settings are inherited to the child socket after accept().
The following two options apply to CCID 3 exclusively and are getsockopt()-only.
In either case, a TFRC info struct (defined in <linux/tfrc.h>) is returned.