Until these numbers do not exceed total amount of RAM, this is exactlyQuote:> of errors a bit but I'm not sure I fully understand the implications of
> doing so.
the action required in this case.
Dumps, which you sent to me, show nothing pathological. Actually,
they are made in some period of full peace: only 47 orphans and
only about 10MB of accounted memory.
This is not essential with 2.4. In 2.4 this state does not grab any essentialQuote:> echo 30 > /proc/sys/net/ipv4/tcp_fin_timeout
Why?Quote:> echo 0 > /proc/sys/net/ipv4/tcp_timestamps
> echo 0 > /proc/sys/net/ipv4/tcp_sack
If you still have problems with orphans, you should raise theseQuote:> echo "3072 3584 6144" > /proc/sys/net/ipv4/tcp_mem
numbers. Extremal settings are sort of:
Z=<total amount of ram in pages>
Y=<something < Z>
Z=<something < Y>
echo "$X $Y $Z" > /proc/sys/net/ipv4/tcp_mem
Set them to maximum and if the messages will not disappear completely,
decrease them to more tough limits.
Normal. Debugging.Quote:> Feb 18 15:05:44 mcquack kernel: sending pkt_too_big to self
Debugging too.Quote:> Feb 18 15:24:07 mcquack kernel: TCP: peer xx.xx.xx.xx:1084/7000 shrinks
> window 2106777705:1072:2106779313. Bad, what else can I say?
Number Z is exceeded, newly _closed_ sockets will be aborted andQuote:> Feb 18 15:42:06 mcquack kernel: TCP: dbg sk->wmem_queued 5664
> tcp_orphan_count 99 tcp_memory_allocated 6145
stack entered state of moderation of its appetite.
Dump, which you have sent to me and further messages in logs,
show that it succeded and converged to normal state.
Actually, the only dubious place in your original report was somethingQuote:> Please let me know if I can provide more debug info or test something!
about behaviour of ssh. ssh surely cannot be affected by this effect.
Could you elaborate this? What kind of problem exactly? Maybe, some
tcpdump is the problem is reproducable.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/