From: "zhao, forrest" <forrest.zhao@intel.com>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
linux-mtd@lists.infradead.org
Subject: Some thoughts about JFFS3 design doc
Date: Mon, 14 Nov 2005 17:51:15 +0800 [thread overview]
Message-ID: <1131961875.3417.35.camel@localhost.localdomain> (raw)
Hi, Artem
I read through your JFFS3 design doc and had some thoughts
1 in Section 4.1->4, there's a typo:
direntries contain {xattr name =>xattr ID}......
2 in section 3.6, I think it's better if you could
give a description or an example of how to replay
the journal to build the journal tree in RAM and
recover the inconsistent meta data on flash.
3 In section 4, I think it's better if you could
give a description or an example of what happens
for an update operation. Such as what happens when
a write operation update offset from 100 to 200 for
a file of length 400 bytes. I guess maybe you are
working on this now :)
4 I think your design doc is well-organized and give
reader a very clear picture and illustration of the
JFFS3 design.
Thanks,
Forrest
next reply other threads:[~2005-11-14 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 9:51 zhao, forrest [this message]
2005-11-14 10:39 ` Some thoughts about JFFS3 design doc Artem B. Bityutskiy
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=1131961875.3417.35.camel@localhost.localdomain \
--to=forrest.zhao@intel.com \
--cc=dedekind@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