public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: landley@trommello.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_TINY
Date: Mon, 04 Nov 2002 16:30:11 -0600	[thread overview]
Message-ID: <3DC6F4F3.5010801@inet.com> (raw)
In-Reply-To: 200211041616.48602.landley@trommello.org

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

Rob Landley wrote:
> On Monday 04 November 2002 20:34, Cort Dougan wrote:
> 
>>I'm with you on that.  People who clammer ignorantly about image size
>>without looking at what they actually need should have opened their eyes in
>>the last few years.  Flash and RAM sizes under 32M are nearly unheard of
>>now-a-days.
> 
> 
> How much power does flash eat?  I was under the impression half the reason for 
> tiny amounts of memory was to increase battery life in things that really 
> should last weeks or months instead of hours (wristwatches, cell phones on 
> standby, etc), but I guess that's mostly a question of dram and sram, not 
> flash.  (I take it you can read the heck out of it without wearing it out, 
> it's just writes that are a problem...  Then again you don't want rapidly 
> rewritten bookkeeping stuff in flash, do you?  (Jiffies, scheduler stuff, 
> etc, should not be in flash...))

There a couple of kinds of flash memory that have different properties 
in the writes...
The one I'm more familiar with allows you to change any '1' bit to a '0' 
bit on a bit-by-bit basis, but it is, ehm, a tad slow.  But if you want 
to change a '0' bit to a '1' bit, you have to erase a 16 or 32 kB block 
to all '1' bits, and that is, well, very slow.
(Storing 'jiffies' in flash, given that updating the jiffies would take 
multiple jiffies would be, well, 'fun'. ;) I could, however, see some 
sense in running the read-only parts of the kernel directly from flash...)
It's been a while since I looked at read times, but I expect it to be 
essentially memory speeds.

 > Not my area, I'm afraid...
 >
 > Rob

Just an FYI, in case you're curious.

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------

[-- Attachment #2: Type: text/plain, Size: 701 bytes --]

---------------------------------------------------------

Confidentiality Notice:    This e-mail transmission may contain
confidential and/or privileged information that is intended only for 
the individual or entity named in the e-mail address.  If you are not the
intended recipient, you are hereby notified that any disclosure,
copying, distribution or reliance upon the contents of this e-mail
message is strictly prohibited. If you have received this e-mail
transmission in error, please reply to the sender, so that proper
delivery can be arranged, and please delete the message from your
computer.  Thank you.
Inet Technologies, Inc.

---------------------------------------------------------

  reply	other threads:[~2002-11-04 22:23 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 22:36 CONFIG_TINY Rasmus Andersen
2002-10-30 23:48 ` CONFIG_TINY Rik van Riel
2002-10-31  0:53 ` CONFIG_TINY Adrian Bunk
2002-10-31  1:10   ` CONFIG_TINY Tom Rini
2002-10-31  5:33     ` CONFIG_TINY Mark Mielke
2002-10-31 14:33       ` CONFIG_TINY Tom Rini
2002-10-31 16:51         ` CONFIG_TINY Mark Mielke
2002-10-31 17:04           ` CONFIG_TINY Tom Rini
2002-10-31 17:12             ` CONFIG_TINY Mark Mielke
2002-10-31 17:24               ` CONFIG_TINY Tom Rini
2002-10-31 17:49                 ` CONFIG_TINY Sam Ravnborg
2002-10-31 18:11                   ` CONFIG_TINY Tom Rini
2002-11-01  2:09                 ` CONFIG_TINY Bill Davidsen
2002-11-01 14:12                   ` CONFIG_TINY Tom Rini
2002-10-31 18:26             ` CONFIG_TINY Kent Borg
2002-10-31 18:53               ` CONFIG_TINY Tom Rini
2002-11-04  2:13                 ` CONFIG_TINY Rob Landley
2002-11-04 19:50                   ` CONFIG_TINY Tom Rini
2002-11-04 20:34                     ` CONFIG_TINY Cort Dougan
2002-11-04 16:16                       ` CONFIG_TINY Rob Landley
2002-11-04 22:30                         ` Eli Carter [this message]
2002-11-01  2:10             ` CONFIG_TINY Arnaldo Carvalho de Melo
2002-10-31 21:12           ` CONFIG_TINY Luc Van Oostenryck
2002-10-31 17:08         ` CONFIG_TINY Matt Porter
2002-10-31 16:52           ` CONFIG_TINY Bernd Petrovitsch
2002-10-31 18:43             ` CONFIG_TINY Rasmus Andersen
2002-10-31 19:15               ` CONFIG_TINY Tom Rini
2002-10-31 19:27                 ` CONFIG_TINY Rasmus Andersen
2002-11-01 14:19                   ` CONFIG_TINY Tom Rini
2002-10-31 23:30               ` CONFIG_TINY Bernd Petrovitsch
2002-11-01  6:17                 ` CONFIG_TINY Rasmus Andersen
2002-11-01 22:05                   ` CONFIG_TINY Bernd Petrovitsch
2002-11-01 22:10                     ` CONFIG_TINY Rasmus Andersen
2002-11-01  2:03     ` CONFIG_TINY Bill Davidsen
2002-11-01 14:15       ` CONFIG_TINY Tom Rini
2002-11-04  2:13         ` CONFIG_TINY Rob Landley
2002-11-04 19:51           ` CONFIG_TINY Tom Rini
2002-11-04 16:09             ` CONFIG_TINY Rob Landley
2002-11-05 19:26             ` CONFIG_TINY Bill Davidsen
2002-11-05 19:56               ` CONFIG_TINY Tom Rini
2002-11-05 17:55                 ` CONFIG_TINY Rob Landley
2002-11-06  2:05                   ` CONFIG_TINY Tom Rini
2002-11-06 14:35                   ` CONFIG_TINY Bill Davidsen
2002-11-05 19:59               ` CONFIG_TINY Alan Cox
2002-10-31  8:24   ` CONFIG_TINY Rasmus Andersen
2002-10-31 10:05     ` CONFIG_TINY Erik Andersen
2002-10-31 10:08       ` CONFIG_TINY Rasmus Andersen
2002-10-31 11:08         ` CONFIG_TINY Erik Andersen
2002-10-31 19:33     ` CONFIG_TINY Daniel Egger
2002-10-31 19:55       ` CONFIG_TINY Rasmus Andersen
2002-10-31  8:32 ` CONFIG_TINY Jens Axboe
2002-10-31  8:53   ` CONFIG_TINY Rasmus Andersen

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=3DC6F4F3.5010801@inet.com \
    --to=eli.carter@inet.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.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