[RTEMS Project] #3476: IMFS - Improve Bytes Per Block Handling

[RTEMS trac]

#3476: IMFS - Improve Bytes Per Block Handling
-----------------------------------------+-------------------------
 Reporter:  Joel Sherrill                |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Indefinite
Component:  fs                           |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  SoC, API, small, filesystem  |  Blocked By:
 Blocking:                               |
-----------------------------------------+-------------------------
Changes (by Joel Sherrill):

 * version:  5 =>


Old description:

> This ticket involves improvements to the IMFS bytes per block behavior.
> These changes will also need to be reflected in user facing
> documentation.
>
> * Currently, the behavior when presented when an invalid configuration
> value for bytes per block is to silently use the default. It is likely
> preferable to have a fatal error.
>
> * Allow for larger block sizes. When implemented, a block size of 512
> which resulted in a maximum file size of 1GB was near unimaginable for an
> embedded system. Allowing for a maximum of at least 1K and possibly 2K
> seems reasonable now. Note that adding new block size options requires
> calculating the corresponding maximum file sizes and updating imfs.h and
> user facing documentation.
>
> Possible Mentors: Joel Sherrill
> Skills: C
> Difficulty: Easy

New description:

 This ticket involves improvements to the IMFS bytes per block behavior.
 These changes will also need to be reflected in user facing documentation.

 * Currently, the behavior when presented when an invalid configuration
 value for bytes per block is to silently use the default. It is likely
 preferable to have a fatal error.

 * Allow for larger block sizes. When implemented, a block size of 512
 which resulted in a maximum file size of 1GB was near unimaginable for an
 embedded system. Allowing for a maximum of at least 1K and possibly 2K
 seems reasonable now. Note that adding new block size options requires
 calculating the corresponding maximum file sizes and updating imfs.h and
 user facing documentation.

 Possible Mentors: Joel Sherrill
 Skills: C
 Difficulty: Easy

 Note: For a SoC project, this may be combined with #3477 to make a large
 project.

--

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