git.openpandora.org
/
pandora-kernel.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/cooloney...
[pandora-kernel.git]
/
Documentation
/
networking
/
udplite.txt
diff --git
a/Documentation/networking/udplite.txt
b/Documentation/networking/udplite.txt
index
6be09ba
..
855d8da
100644
(file)
--- a/
Documentation/networking/udplite.txt
+++ b/
Documentation/networking/udplite.txt
@@
-12,7
+12,7
@@
For in-depth information, you can consult:
o The UDP-Lite Homepage: http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/
For in-depth information, you can consult:
o The UDP-Lite Homepage: http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/
- Fom here you can also download some example application source code.
+ F
r
om here you can also download some example application source code.
o The UDP-Lite HOWTO on
http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/files/UDP-Lite-HOWTO.txt
o The UDP-Lite HOWTO on
http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/files/UDP-Lite-HOWTO.txt
@@
-148,7
+148,7
@@
getsockopt(sockfd, SOL_SOCKET, SO_NO_CHECK, &value, ...);
is meaningless (as in TCP). Packets with a zero checksum field are
getsockopt(sockfd, SOL_SOCKET, SO_NO_CHECK, &value, ...);
is meaningless (as in TCP). Packets with a zero checksum field are
- illegal (cf. RFC 3828, sec. 3.1) will be silently discarded.
+ illegal (cf. RFC 3828, sec. 3.1)
and
will be silently discarded.
4) Fragmentation
4) Fragmentation
@@
-223,7
+223,7
@@
While it is important that such cases are dealt with correctly, they
are (annoyingly) rare: UDP-Lite is designed for optimising multimedia
performance over wireless (or generally noisy) links and thus smaller
While it is important that such cases are dealt with correctly, they
are (annoyingly) rare: UDP-Lite is designed for optimising multimedia
performance over wireless (or generally noisy) links and thus smaller
- coverage leng
ht
s are likely to be expected.
+ coverage leng
th
s are likely to be expected.
V) UDP-LITE RUNTIME STATISTICS AND THEIR MEANING
V) UDP-LITE RUNTIME STATISTICS AND THEIR MEANING
@@
-236,7
+236,7
@@
This displays UDP-Lite statistics variables, whose meaning is as follows.
This displays UDP-Lite statistics variables, whose meaning is as follows.
- InDatagrams: T
otal number of received datagram
s.
+ InDatagrams: T
he total number of datagrams delivered to user
s.
NoPorts: Number of packets received to an unknown port.
These cases are counted separately (not as InErrors).
NoPorts: Number of packets received to an unknown port.
These cases are counted separately (not as InErrors).
@@
-259,7
+259,7
@@
VI) IPTABLES
There is packet match support for UDP-Lite as well as support for the LOG target.
VI) IPTABLES
There is packet match support for UDP-Lite as well as support for the LOG target.
- If you copy and paste the following line into /etc/protcols,
+ If you copy and paste the following line into /etc/prot
o
cols,
udplite 136 UDP-Lite # UDP-Lite [RFC 3828]
udplite 136 UDP-Lite # UDP-Lite [RFC 3828]