> syslogd is the most prominent user of fsync() and log files tend to grow
> big..
Also, they tend to be _appended_ to... Usually only one block
would need to be synced. Couldn't there be a way of detecting
this special case.
Another strategy might be to just walk though the buffer cache
and sync all buffers associated with that file... A linear mem
walk is quite fast, and the test is very fast. We just need to
look at the 'page->inode' and see if this is the inode we want
to flush.
Rik.
----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...