public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Doug Fraser <dfraser@photuris.com>
To: 'Thomas Koeller' <thomas.koeller@baslerweb.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Stress testing JFFS2
Date: Wed, 15 Oct 2003 18:33:00 -0000	[thread overview]
Message-ID: <E2D27064CD59574F88D05AEF5728396D0159036E@PH01SRV02.photuris.com> (raw)

It becomes an interesting issue when you are using the FLASH
to store an actively updated database, which moves through
the FLASH arena at some slow but consistent rate.

Doug Fraser
dfraser@photuris.com

> -----Original Message-----
> From: Thomas Koeller [mailto:thomas.koeller@baslerweb.com]
> Sent: Wednesday, October 15, 2003 7:30 AM
> To: David Woodhouse
> Cc: ecos-discuss@sources.redhat.com; linux-mtd@lists.infradead.org
> Subject: Re: [ECOS] Stress testing JFFS2
> 
> 
> Hi David,
> 
> thanks for your quick response.
> 
> > All correct. But you miss the observation that we also keep a
> > raw_node_ref around for _obsolete_ nodes, which perhaps we 
> could avoid.
> > In fact, we do this because the raw_node_ref is in a 
> singly-linked list,
> > and it's going to be very inefficient to remove obsoleted nodes from
> > that list when they become obsolete.
> 
> I do not think this path leads anywhere I want to go. The flash size
> was chosen to meet the expected storage requirements, which means that
> at some point the flash will be filled with valid data and 
> consequently
> there will be few obsoleted nodes. I expect this to be true for most
> systems.
> 
> > Omitting the 'totlen' field should be relatively simple if 
> you're not
> > freeing obsolete refs. Observe that in 99% of cases, it's true that
> >
> > 	ref->totlen == ref_offset(ref->next_phys) - ref_offset(ref)
> >
> > Make it 100% and make me believe it, and you can remove 
> totlen from the
> > structure.
> >
> 
> I will consider that.
> 
> tk
> --------------------------------------------------
> 
> Thomas Koeller, Software Development
> 
> Basler Vision Technologies
> An der Strusbek 60-62
> 22926 Ahrensburg
> Germany
> 
> Tel +49 (4102) 463-162
> Fax +49 (4102) 463-239
> 
> mailto:thomas.koeller@baslerweb.com
> http://www.baslerweb.com
> 
> ==============================
> 
> 
> -- 
> Before posting, please read the FAQ: 
> http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2003-10-15 18:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 18:33 Doug Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-16  7:23 Øyvind Harboe
2003-10-16  7:32 ` Andrew Lunn
2003-10-16  7:35   ` Øyvind Harboe
2003-10-15 11:53 Dinesh Kumar
2003-10-15 12:54 ` Thomas Koeller
2003-10-08  7:37 Øyvind Harboe
2003-10-08  9:07 ` Jani Monoses
2003-10-15 10:07   ` Thomas Koeller
2003-10-15 10:52     ` David Woodhouse
2003-10-15 11:26       ` Thomas Koeller
2003-10-16 10:25         ` David Woodhouse
2003-10-07 16:43 Øyvind Harboe
2003-10-07 10:57 Øyvind Harboe
2003-10-07 12:31 ` David Vrabel
2003-10-07 13:04 ` Andrew Lunn
2003-10-07 13:16   ` Øyvind Harboe
2003-10-07 13:43     ` Andrew Lunn
2003-10-07 16:42       ` Thomas Koeller
2003-10-07 17:57         ` Andrew Lunn
2003-10-08  8:34           ` Thomas Koeller
2003-10-07 13:36 ` Eric Donnat

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=E2D27064CD59574F88D05AEF5728396D0159036E@PH01SRV02.photuris.com \
    --to=dfraser@photuris.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=thomas.koeller@baslerweb.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 read-only IMAP folder(s) and NNTP newsgroup(s).