I don't expect this to work because the readonly side can't know when the
incore informations outdates.
Yes, it can be a problem, but may be this may be solved by disabling any
cache on read-only side (or setting expire time in one sec) ?
You can't diable readcaching completely.
Say you need the inode, then you will read it and finaly use it.
You don't reread it for every single byte you access which creates some kind of
read cache. And there are much more complex points like this sample.
Ok, have kernel algorithm to "expire" cached vnodes ? Or vnodes only
pushed out by new pages ?
In my case writes - relative rare case then reads and I can wait for some
timeout while my in-kernel vnodes will dropped to see new from disk