archive mirror
 help / color / mirror / Atom feed
From: Venkatesh Rao <>
Subject: Problems with tcp_retransmit_skb - Please omit the previous incomplete mail
Date: Thu, 26 Sep 2002 11:46:18 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)

I have a strange problem with tcp_retransmit_skb. I
will describe my setup before i describe my problem.

Please CC me.

ucLinux 2.4.10 based kernel running on a embedded
processor (coldfire) with 40 MIPS processing

This embedded system sends relatively huge amount of
data (~1.5MB/s) over ethernet to a remote system which
process the data. On a normal case it all works great.
But when there is a lot of traffic on the network
(simulated by running flood ping between two desktop
linux systems connected to the same hub as this
embedded system), embedded systems Linux TCP/IP stack
go haywire. 

More details:
Since there is a high traffic on the network, the
embedded system cannot transmit packet and this
triggers tcp retransmit in the stack. 

But the first check on the tcp_transmit_skb fails

if (atomic_read(&sk->wmem_alloc) > min_t(int,
   return -EAGAIN

When conditions fails, the value of wmem_alloc is ~ 
around 56K-154K, sndbuf = 64K and wmem_queued is
around 44K.

Each time it tries to retransmit this if condition
always fail and the whole transmission times out. 

Once this retransmission phase kicks in, even if the
ping flooding is stopped , tcp stack never recovers.

This happens only on the send path of tcp never on the
receive path.

Any hints in  helping me debug this issue will be


Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!

             reply	other threads:[~2002-09-26 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26 18:46 Venkatesh Rao [this message]
2002-09-27  3:53 ` Problems with tcp_retransmit_skb - Please omit the previous incomplete mail kuznet
2002-09-27 14:43   ` Venkatesh Rao
2002-09-27 14:51     ` kuznet
2002-09-29  0:54       ` Venkatesh Rao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).