public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] JFFS2 eats memory
Date: Tue, 13 Jul 2004 08:09:00 -0000	[thread overview]
Message-ID: <1089706190.5995.10.camel@famine> (raw)
In-Reply-To: <20040713075318.GP18802@lunn.ch>

On Tue, 2004-07-13 at 09:53, Andrew Lunn wrote:
> > > Presumably when the raw nodes in the file fragement list are marked as
> > > obsolete, they are no longer required, but are not freed.
> 
> One other thing. You might consider try gettting the garbage collect
> code runnig. This might help solve your problem. 

I just took it for a spin: no change.

This is not surprising. 

There is nothing to garbage collect, i.e. there is plenty of free space
on the JFFS2 drive and very few deleted raw nodes.

> I guess as a proof of concept just call
> jffs2_garbage_collect_pass(JFFS2_SB_INFO(jffs2_sb));
> 
> This is not strictly correct since you need to add locking to one of
> the lists to make this thread safe. I forget which and i've forgotten
> where i read about this, but im sure google will find it for you.
> 
>         Andrew
-- 
Øyvind Harboe
http://www.zylin.com



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

  reply	other threads:[~2004-07-13  8:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 14:42 Øyvind Harboe
2004-07-13  7:40 ` Andrew Lunn
2004-07-13  7:53   ` Andrew Lunn
2004-07-13  8:09     ` Øyvind Harboe [this message]
2004-07-13  8:31     ` Øyvind Harboe
2004-07-13  7:58   ` Øyvind Harboe
2004-07-13  9:30 ` David Woodhouse
2004-07-13  9:49   ` Øyvind Harboe
2004-07-13 10:05     ` David Woodhouse
2004-07-13 10:39       ` Øyvind Harboe
2004-07-13 13:41       ` Øyvind Harboe
2004-07-13 23:01         ` [ECOS] " David Woodhouse
2004-07-14  8:15           ` Øyvind Harboe
2004-07-19 14:25             ` Øyvind Harboe
2004-07-19 15:15               ` David Woodhouse
2004-07-19 16:32                 ` Øyvind Harboe
2004-07-20  6:42                   ` David Woodhouse
2004-07-20  7:51                     ` Øyvind Harboe
2004-07-20 14:25                       ` David Woodhouse
2004-07-20 15:51                         ` Øyvind Harboe
2004-07-20 16:08                           ` David Woodhouse
2004-07-20 20:29                             ` Øyvind Harboe
2004-07-21  2:28                               ` David Woodhouse
2004-07-21  7:54                                 ` Øyvind Harboe
     [not found]                                   ` <1090410703.4280.10.camel@localhost.localdomain>
2004-07-21 12:50                                     ` Øyvind Harboe
2004-07-21 16:33                                       ` David Woodhouse
2004-07-20 13:46                     ` Øyvind Harboe
2004-07-13 10:08     ` [ECOS] " Thomas Koeller
2008-04-08 15:28 Jürgen Lambrecht

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=1089706190.5995.10.camel@famine \
    --to=oyvind.harboe@zylin.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.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).