All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Lou Langholtz <ldl@chpc.utah.edu>
To: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: update on macserial/DMA
Date: Sat, 09 Oct 1999 11:57:40 -0600	[thread overview]
Message-ID: <37FF8214.EB42C5A4@chpc.utah.edu> (raw)
In-Reply-To: 37FD998B.3D0E62B0@chpc.utah.edu


Lou Langholtz wrote:

> Takashi Oe wrote:
>
> > 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. . .
>
> We should probably also clean up the two unneeded buf[64] allocations. These
> would be at lines 1535 and 1572 in Takashi Oe's macserial.c file. They've
> been left over for a few rounds now and I don't see how they're needed for
> anything.

Also, I noticed that while others reported the DMA addition resulted in far
better TCP/IP over PPP performace, I found no such improvement. The difference
seems to be that I've been using the 2.2.12 distribution kernel rather than a
vger kernel and I'll guess that it's the memory management change that accounts
for this. Anyway, I'm going to see if the imporvement will happen now with AC's
2.2.13pre15 kernel with the assumption that the effective memory management
difference is in that. I'm very eager to see the improvements that others have
noted! :-)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-09 17:57 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             ` update on macserial/DMA Takashi Oe
1999-10-06  8:35               ` 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 [this message]
     [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=37FF8214.EB42C5A4@chpc.utah.edu \
    --to=ldl@chpc.utah.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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.