[PATCH 1/2] jffs:2 Move erasing from write_super to GC.

Joakim Tjernlund joakim.tjernlund at transmode.se
Tue Feb 16 06:49:13 EST 2010


Artem Bityutskiy <dedekind1 at gmail.com> wrote on 2010/02/16 10:45:35:
>
> On Tue, 2010-02-16 at 10:18 +0100, Joakim Tjernlund wrote:
> > > Also, I think you should call it with count = 1, so that you would erase
> > > only one EB at one iteration. This way you will let the GC thread do
> > > other things with less latency as well.
> >
> > If we reduce the count to 1 one might just as well remove count from
> > jffs2_erase_pending_blocks() and make it just erase one block on each invocation,
> > not sure I like that as it will be more overhead when erasing many blocks.
> >
> > I figure erasing blocks is the most rewarding form of GC so there should
> > be no need to reduce latency for other things, can you think of a reason?
>
> Hmm, yes, you are right. Please, discard my "erase only 1" suggestion.

OK.

Both you and Kai-Uwe wants back jffs2_erase_pending_trigger() so I will
redo this part.

 Jocke

BTW, I see UBIFS is using CRC16 as well as CRC32. Is there a reason
you are using CRC16 in UBIFS. Any particular reason for that? CRC16 is
much slower than crc32 in linux since the CRC32 impl. was optimized
by yours truly long time ago just because it was impacting mount time
for JFFS2.

   Jocke




More information about the linux-mtd mailing list