From: Takashi Oe <toe@unlserve.unl.edu>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: update on macserial/DMA
Date: Wed, 6 Oct 1999 00:33:58 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.3.96LJ1.1b7.991005234830.1210A-100000@ofey.inetnebr.com> (raw)
In-Reply-To: <19990930183542.004164@mailhost.mipsys.com>
Hi,
I re-wrote the serial DMA support code today and put the patch against
samba/vger linux-2.2.12 source trees (as of tonight) at
ftp://ppc.linux.or.jp/pub/users/toe/serial/.
I think the patch includes most of macserial patches (Ben's and Lou's
are in there, for sure) that I know of.
This code is much better than the previous one in which it was fairly easy
to cause frame/overrun errors, although it was far better than the vanila
macserial (w/o DMA support). To get a feeling of the driver's
performance, I tried the following operations while downloading 10 MB+
files at 49 kbps receiving/33.6 kbps transmitting modem<->ISP and 115 kbps
PMac<->modem (ftp on ppp link):
A: "dd if=/dev/zero of=400MB count=409600 bs=1024; cp 400MB /tmp; rm
400MB"
B: planb+xawtv in grabdisplay mode (~10 fps, 640x480x4 bytes/frame)
With vanila macserial:
"A": ~200 overrun errors; ftp transfers were all aborted.
With previous DMA code:
"A": ~20 frame errors per ~600 packets
"B": a few frame errors per ~50 packets
"A+B": ~30 frame errors and a few overrun errors per ~600 packets
With this new DMA code:
"A" or "B" or "A+B": no error has been observed after about an hour of
trials (I did see a few frame errors when pppd started up once.)
These trials are pretty subjective, but I'm at least glad that it passed
all the tests I tried.
Takashi Oe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-06 5:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37F1AD4B.585E99AB@chpc.utah.edu>
1999-09-29 7:11 ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Geert Uytterhoeven
1999-09-29 7:16 ` Takashi Oe
1999-09-29 7:40 ` Geert Uytterhoeven
1999-09-29 9:13 ` Benjamin Herrenschmidt
1999-09-30 0:46 ` Takashi Oe
1999-09-30 8:50 ` Benjamin Herrenschmidt
1999-09-30 16:21 ` Takashi Oe
1999-09-30 16:35 ` Benjamin Herrenschmidt
1999-10-06 5:33 ` Takashi Oe [this message]
1999-10-06 8:35 ` update on macserial/DMA Benjamin Herrenschmidt
1999-10-06 13:47 ` Takashi Oe
1999-10-06 16:25 ` Benjamin Herrenschmidt
1999-10-06 16:50 ` Benjamin Herrenschmidt
1999-10-08 7:13 ` Lou Langholtz
1999-10-09 17:57 ` Lou Langholtz
[not found] ` <Pine.LNX.3.96LJ1.1b7.991005234830.1210A-100000@ofey.inetne br.com>
1999-10-07 9:48 ` Franz Sirl
1999-10-07 15:37 ` phandel
1999-10-12 7:20 ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Lou Langholtz
1999-09-29 16:44 ` Lou Langholtz
1999-09-29 17:02 ` Benjamin Herrenschmidt
1999-09-29 18:08 ` Lou Langholtz
1999-09-29 18:46 ` Lou Langholtz
1999-09-29 20:00 ` Lou Langholtz
1999-09-30 1:14 ` Takashi Oe
1999-09-30 5:33 ` Geert Uytterhoeven
1999-10-01 13:26 ` Franz Sirl
1999-10-01 13:46 ` Alvin Brattli
[not found] ` <Pine.OSF.3.96.991001153658.16772E-100000@mitra.phys.uit.no >
1999-10-01 14:08 ` Franz Sirl
1999-10-01 16:14 ` Lou Langholtz
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=Pine.LNX.3.96LJ1.1b7.991005234830.1210A-100000@ofey.inetnebr.com \
--to=toe@unlserve.unl.edu \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.