From: Andrew Morton <akpm@digeo.com>
To: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.65-mm1: eth0: Transmit error, Tx status register 90
Date: Tue, 18 Mar 2003 19:18:33 -0800 [thread overview]
Message-ID: <20030318191833.317fa459.akpm@digeo.com> (raw)
In-Reply-To: <20030319013042.19266.qmail@linuxmail.org>
"Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org> wrote:
>
> Hi,
>
> I've been benchmarking file copy operations between 2.5.65-mm1
> and 2.4.20-2.51 since I have noticed that transferring files from my
> 2.4.20 machine to 2.5.65-mm1 gives an steady 10MBps throughput
> but doing the opposite (from 2.5.65-mm1 to 2.4.20) gives me a
> mere 3MBps throughput.
Is it slow with both scp and NFS? Or just NFS?
If just NFS then yes, I see this too. Transferring files 2.5->2.4 over NFS
is several times slower than 2.4->2.4 or 2.5->2.5. Quite repeatable.
> After transferring a 256MB file using NFS and SCP, I have noticed
> several "eth0: Transmit error, Tx status register 90.". I have attached
> dmesg output, ioports, iomem, lsmod and lspci.
That's a transmit underrun. The PCI/memory system was not able to feed data
into the NIC fast enough.
Please determine when this started. 2.5.64 would be a good kernel to test
because it doesn't have the PCI changes.
next prev parent reply other threads:[~2003-03-19 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 1:30 2.5.65-mm1: eth0: Transmit error, Tx status register 90 Felipe Alfaro Solana
2003-03-19 3:18 ` Andrew Morton [this message]
2003-03-19 19:03 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2003-03-19 11:24 Felipe Alfaro Solana
2003-03-19 11:32 ` Andrew Morton
2003-03-19 12:44 Felipe Alfaro Solana
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=20030318191833.317fa459.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.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