fsync can be dramatically better optimized, and it will be after the kernel merge work is completed. This optimization will likely consist of reducing the tendency to merge atoms and handling fsync by using write twice algorithms to a fixed journal area. Other improvements will doubtless be found when time is spent on it. I am sorry that vim and evolution are suffering so much from our neglecting fsync until after the merge. fsync is one of the things I would have us working on if I had my choice of what we improved in reiser4 rather than other persons making that choice for us at the moment. Oh well, such is life in the society of men.;-)
It looks like akpm is going to start reading the reiser4 code. I suspect his remarks will be a step above the ones made so far, he wrote such nice readahead code.
