From: Dan Malek <dan@netx4.com>
To: Alan Mimms <alan@packetengines.com>
Cc: Richard Hendricks <ra6353@email.sps.mot.com>,
Jim Chapman <jim.chapman@iname.com>,
bsimon@ctam.com.au,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc-embedded: /bin/sh wont run from nfsroot.
Date: Wed, 15 Dec 1999 17:13:33 -0500 [thread overview]
Message-ID: <3858128D.B2A8D870@netx4.com> (raw)
In-Reply-To: 99121513483409.00750@alan.corp.packetengines.com
Alan Mimms wrote:
> Actually and arguably, "good system design" says precisely the opposite. If
> you're building up, say, network protocol packets to be DMAed out through a FEC
> you want to be able to touch the area of the packet buffer repeatedly without
> having to do a memory cycle for each "touch". Cacheable packet buffers are the
> only way to get this performance enhancing behavior.
This is exactly what the Linux kernel does. It just didn't
seem to be the place to describe what is cached and flushed,
write through, or non-cached. Take a look at the existing
CPM drivers and see what they do.
A "good system design" is whatever is appropriate for the
application. Be happy you are using a processor that provides
these flexible options. Many don't.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-15 22:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 5:55 linuxppc embedded boot problems Brian Kuschak
1999-12-15 5:22 ` linuxppc-embedded: /bin/sh wont run from nfsroot Brendan Simon
1999-12-15 11:00 ` Jim Chapman
1999-12-15 18:56 ` Alan Mimms
1999-12-15 20:09 ` Dan Malek
1999-12-15 21:27 ` Richard Hendricks
1999-12-15 21:37 ` Alan Mimms
1999-12-15 22:13 ` Dan Malek [this message]
1999-12-16 14:52 ` Richard Hendricks
1999-12-15 19:24 ` Dan Malek
1999-12-15 23:10 ` linuxppc-embedded: memory map question Brendan Simon
1999-12-16 9:37 ` linuxppc-embedded: programs wont run from nfsroot Brendan Simon
1999-12-15 22:40 ` linuxppc-embedded: /bin/sh " Brendan Simon
1999-12-16 0:24 ` Brendan Simon
1999-12-16 2:17 ` Brendan Simon
1999-12-15 19:11 ` Dan Malek
[not found] ` <ot66y035bv.fsf@thinktwice.zoftcorp.dk>
1999-12-15 22:29 ` Brendan Simon
1999-12-15 19:06 ` linuxppc embedded boot problems Dan Malek
1999-12-15 22:56 ` Brendan Simon
1999-12-16 5:03 ` 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=3858128D.B2A8D870@netx4.com \
--to=dan@netx4.com \
--cc=alan@packetengines.com \
--cc=bsimon@ctam.com.au \
--cc=jim.chapman@iname.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ra6353@email.sps.mot.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 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).