|
From: Hartmut B. <har...@te...> - 2001-11-08 18:01:45
|
> The recent changes to vfat to make it asynchronous look to be a hack to > queue work items to worker threads to actually do the IO synchronously > there instead of in the calling thread. A FSD handle all accesses to files synchronous. There are some differences between read/write and paged/nonpaged operations. When the caller can't block, the FSD handle the request in created thread. Why can't a FSD not use the worker queue from kernel? > While this may suffice to support > async IO for now, it is a dirty hack, and async IO needs to be implemented > properly, which imho, requires a large rewrite of the vfat driver. I ask, > why waste time with this hack instead of rewriting the code to work properly? Correct, the vfat driver must be rewritten. But the driver needs also more support from kernel. There is no implementation of a cache manager like NT, the security functions doesn't work and many other functions doesn't work under special conditions. I think, at the moment it's better to add some function to vfat in small steps and test it with the current kernel. - Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |