From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "'David Woodhouse'" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: JFFS2 ram memory usage
Date: Thu, 7 Aug 2003 13:08:15 +0200 [thread overview]
Message-ID: <002001c35cd4$33139790$73dea8c0@lair> (raw)
In-Reply-To: <1060253873.25209.61.camel@passion.cambridge.redhat.com>
>You could also remove the actual compression routines if
>you're going to do that.
In my patch I:
- removed the allocation of the compression/decompression buffer
that the compression routines uses to attempt to compress.
- removed the invocation of the compression/decompression call.
>Other users, especially eCos users, may want to individually
>select the compression algorithms available too.
Agreed.
I haven't checked, but I can't imagine that the runlength
compressor using a lot of memory.
>Finding a way to eliminate the 'totlen' field of the
>jffs2_raw_node_ref structure might be productive. Or possibly
>making the jffs2_raw_node_ref contain doubly-linked lists if
>that then means we can discard obsolete nodes immediately
>rather than keeping them around.
I don't speak enough JFFS2 currently to comfortably attempt this.
Øyvind
prev parent reply other threads:[~2003-08-07 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 9:42 JFFS2 ram memory usage Øyvind Harboe
2003-08-07 10:57 ` David Woodhouse
2003-08-07 11:08 ` Øyvind Harboe [this message]
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='002001c35cd4$33139790$73dea8c0@lair' \
--to=oyvind.harboe@zylin.com \
--cc=dwmw2@infradead.org \
--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