From: Matej Kupljen <matej.kupljen@ultra.si>
To: pantelis.antoniou@gmail.com
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: smc91x support
Date: Thu, 10 Nov 2005 18:44:30 +0100 [thread overview]
Message-ID: <1131644670.1478.4.camel@orionlinux.starfleet.com> (raw)
In-Reply-To: <200511101737.09316.pantelis.antoniou@gmail.com>
Hi
> > matej> Is there any solution to this?
> >
> > I have similar problem on my several custom boards with SMC91C111. I
> > see so many RX overrun, but I can not see why it happens. Forcing to
> > 10Mbps/HalfDuplex reduced the overrun count (and works better than
> > 100Mbps), but it is not preferable, of course ...
How did you achieve this? By software or by using 10 Mbps switch?
> And yes performance is bad with this chip.
Probably I'll try and switch it to 10 Mbps, because NFS is terrible
because it gets a lot of timeouts because of dropped packets.
> I'm not sure if DMA would
> help much, since the overrun occurs because the chip does not have
> enough internal buffers. I don't think that we can service the interrupts
> fast enough to prevent the overruns...
I found this mail from Nicolas on ARM mailing list:
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-October/031736.html
Maybe we could try DMA and see what happens.
Any hints how to try this, because I haven't worked with DDMA before?
BR,
Matej
next prev parent reply other threads:[~2005-11-10 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 14:52 smc91x support Matej Kupljen
2005-11-10 15:15 ` Atsushi Nemoto
2005-11-10 15:37 ` Pantelis Antoniou
2005-11-10 17:44 ` Matej Kupljen [this message]
2005-11-11 1:36 ` Atsushi Nemoto
2005-11-10 15:29 ` Pete Popov
2005-11-10 17:52 ` Matej Kupljen
2005-11-10 17:56 ` Peter Popov
2006-01-04 21:23 ` Matej Kupljen
2006-01-05 2:42 ` Pete Popov
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=1131644670.1478.4.camel@orionlinux.starfleet.com \
--to=matej.kupljen@ultra.si \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=pantelis.antoniou@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