From: Jesper Krogh <jesper@krogh.cc>
To: David Miller <davem@davemloft.net>
Cc: yhlu.kernel@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24)
Date: Mon, 12 May 2008 08:52:32 +0200 [thread overview]
Message-ID: <4827E930.3000008@krogh.cc> (raw)
In-Reply-To: <20080510.213431.193696750.davem@davemloft.net>
David Miller wrote:
> From: Jesper Krogh <jesper@krogh.cc>
> Date: Sat, 10 May 2008 13:01:08 +0200
>
>> Any good suggestions about the "Transmit timed out" messages. It
>> currently leads to a system that "doesnt die" but doesnt respond within
>> 15 minutes of load of the network adapter.
>
> It's likely some bug in the driver that hangs the card for whatever
> reason, which we'll need to work out.
Ok. I have been testing a bit more. It generally works fine, It seems
the "transmit timed out" thing was provoked by dd in the tests, because
it was creating a lot of small requests. (default bs=512).(over NFS).
When the blocksize went up, the problem dissapered. (and the numer of
context-switches went down).
When the blocksize went up, the performance likewise raised to 615MB/s.
I haven't been able to get pass that number.
This is where one of the cpu's are settling at 100% load.
Jesper
--
Jesper
next prev parent reply other threads:[~2008-05-12 6:52 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4821F3B7.2090702@krogh.cc>
[not found] ` <86802c440805071130m62c1f4edydb3316dac4a2aba2@mail.gmail.com>
2008-05-07 21:15 ` NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24) David Miller
2008-05-09 18:32 ` Jesper Krogh
2008-05-09 21:32 ` David Miller
2008-05-09 21:59 ` Jesper Krogh
2008-05-09 22:07 ` David Miller
2008-05-09 22:13 ` Jesper Krogh
2008-05-09 22:09 ` Matheos Worku
2008-05-09 22:15 ` Jesper Krogh
2008-05-09 22:36 ` Matheos Worku
2008-05-09 22:43 ` Matheos Worku
2008-05-09 22:46 ` David Miller
2008-05-09 23:10 ` Jesper Krogh
2008-05-09 23:21 ` Matheos Worku
2008-05-09 22:45 ` David Miller
2008-05-22 16:32 ` Jesper Krogh
2008-05-22 17:15 ` Ben Hutchings
2008-05-22 17:41 ` David Miller
2008-05-22 18:14 ` Ben Hutchings
2008-05-22 18:28 ` David Miller
2008-06-01 7:25 ` Andrey Panin
2008-06-01 16:01 ` David Miller
2008-05-09 22:20 ` Rick Jones
2008-05-09 22:48 ` Jesper Krogh
2008-05-09 23:03 ` Rick Jones
2008-05-09 23:13 ` Jesper Krogh
2008-05-09 23:33 ` Rick Jones
2008-05-09 23:08 ` David Dillow
2008-05-10 6:22 ` Jesper Krogh
2008-05-10 15:53 ` Roland Dreier
2008-05-12 6:49 ` Jesper Krogh
2008-05-10 2:20 ` Bill Fink
2008-05-10 11:01 ` Jesper Krogh
2008-05-11 4:34 ` David Miller
2008-05-11 5:44 ` Jesper Krogh
2008-05-11 6:08 ` David Miller
2008-05-11 9:47 ` Jesper Krogh
2008-05-12 6:52 ` Jesper Krogh [this message]
2008-05-26 19:03 ` Jesper Krogh
2008-05-26 19:33 ` David Miller
2008-05-26 19:39 ` David Miller
2008-05-26 20:54 ` Jesper Krogh
2008-05-26 22:15 ` David Miller
2008-05-26 22:21 ` Jesper Krogh
2008-05-26 22:30 ` David Miller
2008-05-27 6:19 ` Jesper Krogh
2008-05-28 1:18 ` Matheos Worku
2008-05-29 5:34 ` David Miller
2008-05-30 0:14 ` Matheos Worku
2008-05-30 7:00 ` David Miller
2008-06-16 18:09 ` Matheos Worku
2008-06-16 18:21 ` Jesper Krogh
2008-06-18 0:02 ` David Miller
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=4827E930.3000008@krogh.cc \
--to=jesper@krogh.cc \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/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).