RTEMS Block Driver Execution Flow

[Chris Johns]

On 19/5/18 9:45 am, Joel Sherrill wrote:
> I am starting to write a block driver which doesn't have a media matching
> any of the existing ones. I was trying to get a feel for the flow of operations
> and having trouble figuring it out. flashdisk looks to be a good guide except 
> it is using rtems_disk_create_phys() which #3358 marks as deprecated. 
> RAM disk and NV disk still use it also.
> 
> Where's the best discussion of this?
> 

Doxygen's ...

https://docs.rtems.org/doxygen/branches/master/group__rtems__libblock.html

?

>  Any other guidance?

As documented in the "Detailed Description" section

https://docs.rtems.org/doxygen/branches/master/group__rtems__bdbuf.html#details

the pool's memory can be used in pools of different sizes. This lets you have a
block size to read a file system's details from a superblock of some form and
from that the file system's block size which is then set.

The output workers can run in parallel if you have separate drivers configured.

I hope this helps.

Chris