linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "Dan Malek" <dan@embeddededge.com>
Cc: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>,
	"Robert P. J. Day" <rpjday@mindspring.com>
Subject: Re: value of XIP?  and whether it works with 2.6 kernel?
Date: Wed, 25 Aug 2004 12:10:31 -0400	[thread overview]
Message-ID: <001a01c48abe$0fccb5f0$0301a8c0@chuck2> (raw)
In-Reply-To: FE902A72-F6AB-11D8-918A-003065F9B7DC@embeddededge.com


>
> On Aug 25, 2004, at 7:22 AM, Mark Chambers wrote:
>
> > The main value, I believe, is as part of a rapid boot setup - you can
> > avoid the decompress and copy phase.
>

Dan Malek responded:

> The XIP has little effect on this.  Wolfgang hit the important points.
> I originally did XIP on the 8xx many years ago for an embedded
> appliance that was DRAM challenged.  It saved a little memory,
> but along with it came the pinned TLB which helped a little with
> performance.
>

I guess I wasn't basing my comment exclusively on 8xx, but thinking
more of the general linux quick boot work being done, as in this
paper from the linux 2004 symposium (see section 4):
http://www.finux.org/Reprints/Reprint-Bird-OLS2004.pdf
So, in other words, maybe XIP will come back again?


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

  reply	other threads:[~2004-08-25 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 15:44 value of XIP? and whether it works with 2.6 kernel? Robert P. J. Day
2004-08-25  7:55 ` Wolfgang Denk
2004-08-25 11:22 ` Mark Chambers
2004-08-25 15:32   ` Dan Malek
2004-08-25 16:10     ` Mark Chambers [this message]
2004-08-25 17:01       ` Dan Malek
2004-08-26  1:27         ` David Woodhouse
2004-08-26  3:45           ` 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='001a01c48abe$0fccb5f0$0301a8c0@chuck2' \
    --to=markc@mail.com \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rpjday@mindspring.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).