| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
|
| |
|
|
| |
Submitted by: Paul
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Delete redundant declarations.
- Add -Wredundant-declarations to Makefile.i386 so they don't come back.
- Delete sloppy COMMON-style declarations of uninitialized data in
header files.
- Add a few prototypes.
- Clean up warnings resulting from the above.
NB: ioconf.c will still generate a redundant-declaration warning, which
is unavoidable unless somebody volunteers to make `config' smarter.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
the interface output queue and further udp packets would be fragmented
and only partially sent - keeping the output queue full and jamming the
network, but not actually getting any real work done (because you can't
send just 'part' of a udp packet - if you fragment it, you must send
the whole thing). The fix involves adding a check to make sure that the
output queue has sufficient space for all of the fragments.
|
| |
|
|
|
| |
stall unnecessarily - always send an ACK when a packet len of < mss is
received.
|
| |
|
|
| |
to set it to 4k.
|
| |
|
|
|
| |
a couple of places.
Submitted by: Johannes Helander
|
| |
|
|
|
| |
Reviewed by: Rodney W. Grimes
Submitted by: John Dyson and David Greenman
|
| |\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
|
