* Some thoughts about JFFS3 design doc
@ 2005-11-14 9:51 zhao, forrest
2005-11-14 10:39 ` Artem B. Bityutskiy
0 siblings, 1 reply; 2+ messages in thread
From: zhao, forrest @ 2005-11-14 9:51 UTC (permalink / raw)
To: Artem B. Bityutskiy, linux-mtd
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Some thoughts about JFFS3 design doc
2005-11-14 9:51 Some thoughts about JFFS3 design doc zhao, forrest
@ 2005-11-14 10:39 ` Artem B. Bityutskiy
0 siblings, 0 replies; 2+ messages in thread
From: Artem B. Bityutskiy @ 2005-11-14 10:39 UTC (permalink / raw)
To: zhao, forrest; +Cc: linux-mtd
zhao, forrest wrote:
> Hi, Artem
>
> I read through your JFFS3 design doc and had some thoughts
I'm flattered you're reading my writings :-)
> 1 in Section 4.1->4, there's a typo:
> direntries contain {xattr name =>xattr ID}......
Oh, thanks.
> 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.
Yes, there is supposed a distinct big chapter related to this topic. I
just have not had time to write it so far.
> 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 :)
Nothing interesting - the new node just goes to the journal and the old
one is considered obsolete.
I'm planning to add a distinct chapter with description of
JFFS3-in0action where this will be described. Thanks for the note.
> 4 I think your design doc is well-organized and give
> reader a very clear picture and illustration of the
> JFFS3 design.
Thanks, the only really major missing thing is Garbage Collection. Will
describe it as soon as I completely design it.
Feel free to send any comments, and even patches - the design sources
are in MTD CVS (Documentation/mtd/).
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-11-14 10:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-14 9:51 Some thoughts about JFFS3 design doc zhao, forrest
2005-11-14 10:39 ` Artem B. Bityutskiy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox