linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: acurtis@onz.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 8260 and skb implementation
Date: Wed, 08 May 2002 01:51:51 -0400	[thread overview]
Message-ID: <3CD8BCF7.1090102@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFGEKKDGAA.acurtis@onz.com


Allen Curtis wrote:

> If you have another 60X bus master, .....

Ah, right, now I remember.

> I do not know how to help you with hardware. I thought that the EST or
> Tundra eval cards had local RAM.

I had one of the original EST boards long ago.  When trying to use
the local RAM it would hang the CPM.  There are remnants of code in
the FCC driver that if enabled would keep the CPM buffer descriptors
and things in the local RAM.

> ... Do you believe moving SKB to local RAM has merit?

I wouldn't make any decisions without some benchmarks, but I suspect
CPM intensive access is more likely to benefit from using the local RAM.
Things like buffer descriptors and ATM control information will likely
win, I don't think SK bufs will because of the high processor core access.

> ... Any oppinion
> about the impact on the zero-copy implementation?

We should make the change to the receive side so this happens.  The
transmit doesn't copy.  I just copied the code from the 8xx long ago
and never made the change.  We can't properly do zero copy receive
on processors that don't have coherent caches due to alignment and
other information potentially shared in a cache line.

Thanks.


	-- Dan


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

  reply	other threads:[~2002-05-08  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 14:34 8260 and skb implementation Allen Curtis
2002-05-07 15:53 ` Dan Malek
2002-05-08  5:17   ` Allen Curtis
2002-05-08  5:51     ` Dan Malek [this message]
2002-05-08 14:18       ` Allen Curtis
2002-05-08 15:21         ` Dan Malek
2002-05-09  1:09       ` Paul Mackerras
2002-05-09 16:26         ` Dan Malek

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=3CD8BCF7.1090102@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=acurtis@onz.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).