[SPAM] Re: P30 flash left in read status mode after a write
Nicolas Pitre
nico at cam.org
Wed Feb 14 16:34:35 EST 2007
On Wed, 14 Feb 2007, Jon Ringle wrote:
> Jörn Engel wrote:
> > On Wed, 14 February 2007 13:52:31 -0500, Jon Ringle wrote:
> >
> >> This did indeed seem to fix the problem, but I'm not sure if I might
> >> inadvertently be causing some side effect. I believe that I might be
> >> taking a slight performance hit to consecutive jffs2 write operations
> >> because now each write operation will need to spend more cycles putting
> >> the flash in to a write mode.
> >>
> >
> > If the performance hit concerns you, you could set a timer instead of
> > changing the chip state. Only if the timer expires - which means that
> > consecutive writes are a non-issue - do you change the chip state.
> >
> >
> Using a timer sounds like a good idea. I'll keep it in mind. I'm not
> sure yet whether I'm concerned about the performance hit as I haven't
> profiled the impact yet. Has anyone got any data that shows what kind of
> improvement jffs2 write operations get with this optimization in place
> to leave flash in read status mode?
It should be fairly minimal. Probably less than 5% difference.
Nicolas
More information about the linux-mtd
mailing list