libblock

[Mick Davis]

Hi

I'm considering implementing a custom filesystem adaptor using the 
libblock. Its for what looks like some fairly unique hardware.  I've 
been looking at the flashdisk and ramdisk examples.

As I see it, I'd implement a 'register' function for the user app to 
run, which uses rtems_disk_create_phys() to connect my ioctrl() 
function.  I'd then get read/write ioctrls containing the blocks.

I'm wondering about how to get somewhat efficient storage.  How is a 
file composed from blocks?  Suppose I have a file containing a few bytes 
of data, how many blocks might my adaptor receive ?

Is the block cache implemented for me? How are written blocks cached 
before writing out to my adaptor?

Will all changed blocks get pushed out when the file is closed after 
writing?

Suppose I need to assemble blocks together for writing in groups. Will 
the cache do this for me? Or can I get a signal when a file is closed?

-- 

Mick Davis
Goanna Technologies Pty Ltd
+61 8 9444 2634