From: Jared Hulbert <jaredeh@gmail.com>
To: dedekind@infradead.org
Cc: David Woodhouse <dwmw2@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
MTD List <linux-mtd@lists.infradead.org>
Subject: Re: JFFS3 memory consumption
Date: Mon, 31 Jan 2005 08:46:46 -0800 [thread overview]
Message-ID: <6934efce05013108463a4d42e4@mail.gmail.com> (raw)
In-Reply-To: <1107111514.18794.37.camel@sauron.oktetlabs.ru>
> 1. For each inode we keep in-core the list of block numbers, where this
> inode's nodes are present. Thus, to build the inode's nodes track, we
> need to read only these summary nodes.
>
> 2. Use ICPs.
I'm not sure I understand the difference. In case 1) are you
suggesting keeping the ICP like data in the summary nodes?
I think the ICP's are a great idea.
next prev parent reply other threads:[~2005-01-31 16:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 8:44 JFFS3 memory consumption Artem B. Bityuckiy
2005-01-26 9:10 ` David Woodhouse
2005-01-26 15:57 ` Artem B. Bityuckiy
2005-01-26 17:06 ` Josh Boyer
2005-01-26 17:11 ` Artem B. Bityuckiy
2005-01-26 18:15 ` David Woodhouse
2005-01-26 18:33 ` Artem B. Bityuckiy
2005-01-26 18:55 ` David Woodhouse
2005-01-27 17:35 ` Artem B. Bityuckiy
2005-01-27 20:23 ` Thomas Gleixner
2005-01-27 22:35 ` David Woodhouse
2005-01-28 0:19 ` Thomas Gleixner
2005-01-28 0:33 ` David Woodhouse
2005-01-28 0:44 ` Thomas Gleixner
2005-01-28 8:45 ` Artem B. Bityuckiy
2005-01-28 9:03 ` Thomas Gleixner
2005-01-28 9:23 ` Artem B. Bityuckiy
2005-01-28 18:57 ` Artem B. Bityuckiy
2005-01-30 18:23 ` Artem B. Bityuckiy
2005-01-30 18:58 ` Artem B. Bityuckiy
2005-01-31 16:46 ` Jared Hulbert [this message]
2005-01-31 18:05 ` Artem B. Bityuckiy
2005-02-01 16:49 ` Thomas Gleixner
2005-02-02 15:44 ` Artem B. Bityuckiy
2005-02-02 18:34 ` Jared Hulbert
2005-02-02 19:02 ` Thomas Gleixner
2005-02-03 10:54 ` Artem B. Bityuckiy
2005-01-28 1:53 ` Josh Boyer
2005-01-28 8:50 ` Artem B. Bityuckiy
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=6934efce05013108463a4d42e4@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.