From: "Kevin D. Kissell" <kevink@mips.com>
To: "Brady Brown" <bbrown@ti.com>, "Nicu Popovici" <octavp@isratech.ro>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: MIPS ftp problem!
Date: Wed, 1 Nov 2000 09:26:46 +0100 [thread overview]
Message-ID: <001501c043dd$7ed69780$066fe8c3@Ulysses> (raw)
In-Reply-To: 39FF2AEB.3137F75E@ti.com
> > I have a problem with the mips machine. I have an Atlas board and when I
> > do ftp on the mips machine from a intel one and I try to transfer files
> > ( it works very very slow 0,0234 bytes/s). The same is happening when I
> > try to make ftp from the mips machine on a intel box ( all running Linux
> > ).
> >
> > Thanks,
> > Nicu
>
> Is this using the Atlas on-board NIC? We found some pretty bad performance
> with the on-board NIC and went to the very cheap RTL8139 PCI card from
> OvisLink (used the 8139too.o driver). Performance there is pretty good.
There seems to be a problem with the on-board NIC on the Philips
multi-I/O part misbehaving under load. It seems to be OK
for TFTP downloading and telnet sessions, but loses packets/interrupts
under FTP or NFS. So I heartily second Brady's recommendation
of using an add-in PCI NIC. At MIPS, we use AMD PCnet cards,
for which there is a MIPS cache-and-endianness-clean driver in the
kernel sources on the MIPS FTP site (and I think built into the kernel
binary there as well).
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Brady Brown <bbrown@ti.com>, Nicu Popovici <octavp@isratech.ro>
Cc: linux-mips@oss.sgi.com
Subject: Re: MIPS ftp problem!
Date: Wed, 1 Nov 2000 09:26:46 +0100 [thread overview]
Message-ID: <001501c043dd$7ed69780$066fe8c3@Ulysses> (raw)
Message-ID: <20001101082646.vBQ039KSbM_3AWKG0kxRNq18JjcaEEg_FJw2CgP5igY@z> (raw)
In-Reply-To: 39FF2AEB.3137F75E@ti.com
> > I have a problem with the mips machine. I have an Atlas board and when I
> > do ftp on the mips machine from a intel one and I try to transfer files
> > ( it works very very slow 0,0234 bytes/s). The same is happening when I
> > try to make ftp from the mips machine on a intel box ( all running Linux
> > ).
> >
> > Thanks,
> > Nicu
>
> Is this using the Atlas on-board NIC? We found some pretty bad performance
> with the on-board NIC and went to the very cheap RTL8139 PCI card from
> OvisLink (used the 8139too.o driver). Performance there is pretty good.
There seems to be a problem with the on-board NIC on the Philips
multi-I/O part misbehaving under load. It seems to be OK
for TFTP downloading and telnet sessions, but loses packets/interrupts
under FTP or NFS. So I heartily second Brady's recommendation
of using an add-in PCI NIC. At MIPS, we use AMD PCnet cards,
for which there is a MIPS cache-and-endianness-clean driver in the
kernel sources on the MIPS FTP site (and I think built into the kernel
binary there as well).
Regards,
Kevin K.
next prev parent reply other threads:[~2000-11-01 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 19:16 MIPS ftp problem! Nicu Popovici
2000-10-31 18:02 ` Jun Sun
2000-10-31 20:26 ` Brady Brown
2000-11-01 8:26 ` Kevin D. Kissell [this message]
2000-11-01 8:26 ` Kevin D. Kissell
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='001501c043dd$7ed69780$066fe8c3@Ulysses' \
--to=kevink@mips.com \
--cc=bbrown@ti.com \
--cc=linux-mips@oss.sgi.com \
--cc=octavp@isratech.ro \
/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