[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: New jffs2 files stay uncompressed?
In my tree, the most time is spent scanning empty flash and doing CRC on the inodes data part. If
there were a way to avoid scanning the empty nodes(that is, play with the ACCURATE bit in the
CLEANMARKER node) and avoid CRC(CRC is checked at every read request anyway so maybe we could just skip
the extra CRC check at mount) at mount on every files data, the mount would be very fast.
BTW, today the CLEANMARKER is optional, is that intentional? If it was mandatory it would
make life simpler when playing with the erase blocks.
> -----Original Message-----
> From: email@example.com]On">mailto:firstname.lastname@example.org]On Behalf
> Of David Woodhouse
> Sent: Monday, February 25, 2002 16:17
> To: Jos Vos
> Cc: email@example.com
> Subject: Re: New jffs2 files stay uncompressed?
> firstname.lastname@example.org said:
> > But... what is the typical mount time of a 110 MB jffs2 (45 MB
> > occupied) on a modern-CPU system?
> Minutes rather than seconds, I'd guess. Wanna implement checkpointing?
> To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
> the body of a message to email@example.com
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to firstname.lastname@example.org