Stopping the GC thread?

[Jörn Engel]

On Thu, 12 June 2003 11:35:59 +0200, Steven Scholz wrote:
> 
> But the impact on system performance done by kupdated is not as 
> critical as the one that's done by the GC intself, is it?

The impact on system performance is practically zero, really.  The
work that GC is doing has to be done anyway.  The only question is,
when will this work be done.

Try the following:
time for i in `seq 10`; do 
	cp $largefile $jffs2;
	sleep 3;
	rm $jffs2/$largefile;
	sleep 3;
done

$largefile should be around 50% or of fs size, roughly.

Run this with and whithout the sleeps.  Notice that the difference it
not just one minute of idle time, it is more in the order of 2,
ignoring the idle time.  And I bet you a fiver that you get the same
order between enabled and disabled GC if you keep the sleep.

GC eats up cpu cycles when the system is idle, so you have more left
when you are under pressure.  And that is a Good Thing(tm).

> >'sector'?  Read http://sources.redhat.com/jffs2/jffs2.pdf 
> I meant flash sectors.

Most people prefer to call them erase blocks or something similar. :)

Jörn

-- 
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein