public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Joshua Wise <joshua@joshuawise.com>
To: Todd Poynor <tpoynor@mvista.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Can jffs2 support XIP extensions?
Date: Tue, 24 Aug 2004 15:10:33 -0400	[thread overview]
Message-ID: <412B92A9.4060901@joshuawise.com> (raw)
In-Reply-To: <412B8EF2.8050606@mvista.com>

> For the kernel boot time it's true that boot times tend to be dominated 
> by the decompression step.  I measured this on a couple platforms at one 
> point (some of my measurements may have been in the OLS presentation, 
> not sure).  I didn't directly measure kernel boot times of an 
> uncompressed non-XIP kernel, but would roughly guess an uncompressed 
> non-XIP kernel would boot to /sbin/init in only about a few tens of 
> milliseconds more time (I'm guessing about the increased time to copy an 
> uncompressed tetx image to RAM) than an XIP kernel on a 266MHz PowerPC 
> 405LP, and 168MHz OMAP ARM 926T is probably similar (it seems to better 
> deal with the cache effects).
Also remember that on many systems, flash is a lot slower than RAM, so 
it is entirely possible that an XIP kernel would actually be _SLOWER_ 
than non-XIP!

joshua

  reply	other threads:[~2004-08-24 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:43 Can jffs2 support XIP extensions? Christopher M Bergeron
2004-08-24 15:10 ` David Woodhouse
2004-08-24 18:27   ` Christopher M Bergeron
2004-08-24 18:50     ` George G. Davis
2004-08-24 18:54   ` Todd Poynor
2004-08-24 19:10     ` Joshua Wise [this message]
2004-08-25  6:08       ` Der Herr Hofrat
2004-08-25 22:04         ` Todd Poynor

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=412B92A9.4060901@joshuawise.com \
    --to=joshua@joshuawise.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tpoynor@mvista.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