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 11:21:01 -0400	[thread overview]
Message-ID: <3CD9425D.2020206@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFCEKODGAA.acurtis@onz.com


Allen Curtis wrote:


>>...I don't think SK bufs will because of the high processor core access.
>
>
> I am not sure what you are saying here?

The advantage of the local RAM is for the CPM to better satisfy its
memory resource requirements by not having to compete with the PowerPC
core (or other bus masters) for 60x bus access.  Since the SK buffers are
predominantly used by the PowerPC core during its IP stack and application
processing, I doubt there is any performance benefit.  However, it isn't
hard to cause SK buffers to be allocated from this memory for testing
purposes, and I would run some benchmarks that represent your application
rather than design by speculation :-)


> You would think that alignment was a common implementation concern.

It's a concern, but we are lucky they are aligned properly.  The transmit
buffers are 16-bit aligned due to the way the headers are built, which
causes trouble for some controllers.


	-- Dan


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

  reply	other threads:[~2002-05-08 15:21 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
2002-05-08 14:18       ` Allen Curtis
2002-05-08 15:21         ` Dan Malek [this message]
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=3CD9425D.2020206@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).