From: Dinesh Kumar <mljangir@yahoo.co.in>
To: ecos-discuss@sources.redhat.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [ECOS] Stress testing JFFS2
Date: Wed, 15 Oct 2003 11:53:00 -0000 [thread overview]
Message-ID: <20031015115257.16327.qmail@web8006.mail.in.yahoo.com> (raw)
> Every operation that changes the contents of the
FLASH
> (even deleting files!)is performed by writing new
> nodes to the FLASH. Every such node is represented
in
> RAM by a struct jffs2_raw_node_ref. The memory
> occupied by these structs is never freed unless the
> file system is unmounted or garbage collection takes
> place.
I am newbie to JFFS2. What is the reason behind not
freeing jffs2_raw_node_ref from RAM (even after they
have been used)?
Regards
Dinesh
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.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
next reply other threads:[~2003-10-15 11:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 11:53 Dinesh Kumar [this message]
2003-10-15 12:54 ` Thomas Koeller
-- 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 18:33 Doug Fraser
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=20031015115257.16327.qmail@web8006.mail.in.yahoo.com \
--to=mljangir@yahoo.co.in \
--cc=ecos-discuss@sources.redhat.com \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).