All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Poor 8260 FCC Ethernet performance
Date: Wed, 09 Jun 2004 16:27:48 -0600	[thread overview]
Message-ID: <1086820067.3643.1766.camel@hermes> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B06DAF8@ismail.innsys.innovsys.com>


On Wed, 2004-06-09 at 16:19, Rune Torgersen wrote:
> Does the FCC performance issue have something to do with the fact that
> the current FCC drivers in linux puts the buffer descriptors in main
> memory and not in dual port?

I hope not since the latest word from Motorola is that they need to be
in main memory - at least on the latest processors, the CPM DPRAM can't
handle cache bursts (or so I've been told - I have a least one customer
that has experienced this)

--
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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

  reply	other threads:[~2004-06-09 22:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 22:19 Poor 8260 FCC Ethernet performance Rune Torgersen
2004-06-09 22:27 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10 19:26 Rune Torgersen
2004-06-09 22:33 Rune Torgersen
2004-06-10 17:56 ` Dan Malek
2004-06-07 17:33 VanBaren, Gerald (AGRE)
2004-06-08  6:29 ` Wojciech Kromer
2004-06-07 12:32 Dayton, Dean
2004-06-07 12:14 Dayton, Dean
2004-06-07 12:16 ` Pantelis Antoniou
2004-06-06 18:00 Adisorn Ermongkonchai
2004-06-07 12:51 ` Mark Chambers
2004-06-07 17:21   ` Adisorn Ermongkonchai
2002-05-31  3:25 Jean-Denis Boyer
2002-05-31  3:42 ` Allen Curtis
2002-05-31 15:51   ` Conn Clark
2002-06-01  3:09     ` Allen Curtis
2002-05-31  3:07 Allen Curtis

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=1086820067.3643.1766.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=runet@innovsys.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 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.