[RTEMS Project] #2844: JFFS2: Add IO controls to get filesystem instance information and force a garbage collection

[RTEMS trac]

#2844: JFFS2: Add IO controls to get filesystem instance information and force a
garbage collection
-----------------------------+------------------------------
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:  4.12
Component:  filesystem       |     Version:  4.11
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |
-----------------------------+------------------------------

Comment (by sebastian.huber):

 Replying to [comment:7 chrisj]:
 > Replying to [comment:2 sebastian.huber]:
 > > Garbage collection is done on demand automatically as late as
 possible. Every operation can result in a garbage collection. We don't
 have a garbage collection thread like on Linux.
 >
 > Is there a special reason we do not have a thread?

 Nobody needed it up to now.

 >
 > > This operation gives you a bit more control when the garbage
 collection takes place.
 >
 > I see it forces a garbage collection so how do you suspend it?
 >
 > Your original post suggested it could be suspended and this would be
 good. After a large delete and reboot the start up can hang on the mount.
 It would be nice to hold this until we have initialised and then let the
 clean up happen.

 With the RTEMS_JFFS2_ON_DEMAND_GARBAGE_COLLECTION and the
 rtems_jffs2_control::trigger_garbage_collection you have now the ability
 to use a garbage collection thread in your application.

--
Ticket URL: <http://devel.rtems.org/ticket/2844#comment:8>
RTEMS Project <http://www.rtems.org/>
RTEMS Project