[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: jffs2_scan_eraseblock() - errors
(Moved to JFFS list).
> > real 47.258s
> With the CRC patch:
> real 36.7s
OK, that's respectable. I just need to finish the other part of the change
-- to actually check the CRCs later on, rather than just leaving them
unchecked. Make sure you take the patch back out of your tree now :)
We may get a little bit more of a speedup when we do that too, as we'll also
stop building up the fragment lists for every inode on mount, but in fact
that code wasn't showing up very high on the profile last time I looked.
> PS: The version of scan.c we are using is 1.57. The patch note was for
Doesn't matter; it's basically the same in both branches.
I suspect that if you profile it now you'll find the most time is taken in
your flash map driver's copy_from routine or memcpy.
I need to implement the XIP scheme which will also allow JFFS2 to directly
access the flash through a kind of pageable ioremap (which handles the times
when the flash is in a mode other than read mode correctly) instead of
having to read into a buffer and work from that. We get to use caches and
burst reads from flash at that point too.
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to email@example.com