From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: "'Tom Rini'" <trini@kernel.crashing.org>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: tx_full v.s tx_free race fix in 8xx_io/enet.c?
Date: Thu, 4 Dec 2003 15:32:04 +0100 [thread overview]
Message-ID: <000201c3ba73$63dba410$0a01a8c0@LUMENTIS02> (raw)
In-Reply-To:
> Something I find a bit odd is that I can run ping -s 1472 -f
> <myTargetIp>
> without problems, but if i "jump start" the ping with "ping
> -s 800 -f <myTargetIp> -l 8"
> I start to loose packages. Ifconfig shows no errors for both cases.
> Do you get the same?
>
> Jocke
Found this problem. It is the backoff/retry logic thats
causing very long TX delays. If I reduce "retlim"(retry limit) from
15 to 6, the system recovers from a large packet ping storm.
Is it a bad idea to reduce the retry limit?
Jocke
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-12-04 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 14:32 Joakim Tjernlund [this message]
2003-12-05 19:53 ` tx_full v.s tx_free race fix in 8xx_io/enet.c? Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 23:00 Joakim Tjernlund
2003-12-03 16:15 ` Tom Rini
2003-12-03 17:08 ` Joakim Tjernlund
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000201c3ba73$63dba410$0a01a8c0@LUMENTIS02' \
--to=joakim.tjernlund@lumentis.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).