(Fwd) Re: DOSFS bug fixes, IDE drivers and sample released

[Angelo Fraietta]

Joel Sherrill wrote:

> Chris Caudle wrote:
>
>>> I have found that listing the directory after closing the file seems 
>>> to do the trick. It must purge the buffers to the disk.
>>>   
>>
>>
>> I haven't looked at the DOSFS code yet, does it have a sync() or 
>> fsync() function?
>> If the file system keeps the allocation table cached in memory, you 
>> may need to flush the allocation table to the storage device, 
>> especially if you are shutting down power on the RTEMS system and 
>> moving the storage device to a different machine (or just re-booting 
>> into Windows, Linux, MacOS etc. on the same machine).
>>  
>>
> Or at least a flush() on the file itself?
> Not to get me started on a tangent but my disertation included some 
> thought on the idea
> that different embedded systems needed different disk caching and 
> scheduling algorithms.
> Ideally those should be selectable on a per-file basis but at a 
> partition level would be
> acceptable.  For example, a write-only log file should have data kept 
> only long enough to
> get it to disk but a sequentially read file could use read-ahead and 
> discard as soon as
> the application read the data.  With some (intelligent) hints from the 
> application,
> the algorithms could be better selected.

I tried fflush (using fopen), without effect. 
-- 
Angelo Fraietta

PO Box 859
Hamilton NSW 2303

Home Page


http://www.users.bigpond.com/angelo_f/

There are those who seek knowledge for the sake of knowledge - that is CURIOSITY
There are those who seek knowledge to be known by others - that is VANITY
There are those who seek knowledge in order to serve - that is LOVE
    Bernard of Clairvaux (1090 - 1153)