From: David Woodhouse <dwmw2@infradead.org>
To: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: remove the 'totlen' field from node_ref
Date: Mon, 15 Nov 2004 09:18:08 +0000 [thread overview]
Message-ID: <1100510289.8015.65.camel@localhost.localdomain> (raw)
In-Reply-To: <419870D4.4050703@yandex.ru>
On Mon, 2004-11-15 at 12:03 +0300, Artem B. Bityuckiy wrote:
> Hello,
>
> I see there were efforts to remove the 'totlen' field from the
> jffs2_raw_node_ref structure. But it is not done yet.
>
> As I understand, in order to succesfullt done this improvements, all the
> space in flash must be represented by means of nodes. This means, we
> should keep padding node references (jffs2_raw_node_ref for paddigs)
> in-core too.
Correct.
> Why is this work not done yet? Are there some difficulties? May be some
> problems arise when we pad to the end of NAND page/Flash block but the
> padding length is not sufficient to write the padding node and we just
> write some pattern?
No, that's not a problem. We can quite happily keep a raw_node_ref which
describes that, and we can do so at mount time too. Mostly we just need
to fix the mount code to generate obsolete node refs for dirty space
rather than just ignoring it and moving on.
Doing that alone is fairly simple. The main reason I haven't done it yet
is because it would need a _lot_ of testing, probably with a period of
checking against the real __totlen field and complaining if they differ.
I haven't really had enough time to do the amount of testing I'd like
before I release such a change.
--
dwmw2
prev parent reply other threads:[~2004-11-15 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 9:03 remove the 'totlen' field from node_ref Artem B. Bityuckiy
2004-11-15 9:18 ` David Woodhouse [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=1100510289.8015.65.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=abityuckiy@yandex.ru \
--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