Hi Bart, >>> [fnodes] are ancient relics that should be done away with. There is no >>> need for them anymore. I'd like to put that high on the priority list >>> for kernel development.
>> in theory you are right. in praxis fnodes are everywhere throughout >> the file system (as you probably know), and there's a reason we left >> them in the kernel the last few years. it's probably fairly easy >> to convert a stable kernel into unstable by trying to convert this. There are fewer and fewer fields for which the difference SFT versus fnode still matters, so I would suggest to slowly "phase out" the old uses of fnodes, field by field and very carefully... > Well, now we have two kinds of f_nodes, the near ones and the far > ones. The far ones are copied to and from near ones using 4 fmemcpy's > in fatfs.c > Replacing the fmemcpy's by a convert fnode to/from SFT function should > be able to eliminate the far fnodes. I'll give that a go. > Once that's done at least some of the fatfs.c functions can be > converted to use SFTs directly. Though this is not as easy as it looks > because fnodes are also used as internal structures for directories. See above - I also think that converting frequently on the fly is not very pleasant performance and complexity wise. No need to hurry in getting rid of the fnodes, so I somehow prefer "phase out style". Eric ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Freedos-kernel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
