Hi,
I am very excited for the fskit changes. Now I finally had some time to actually read the docs. But I am not very sure how the new cache api is able to propagate external file tree changes to fskit. As far as I understand it only handels cached file data but not metadata?
I really hope I am just misunderstanding and this is possible.
Greetings Nils
I am very excited for the FSKit changes. Now I finally had some time to actually read the docs. But I am not very sure how the new cache API is able to propagate external file tree changes to FSKit. As far as I understand it, only handles cached file data but not metadata?
The new cache API is specifically about file data caching, not informing the system about changes generated by external activity (in VFS terms, "vnode_notify"). Note that this also affects the behavior of FSKit objects that are being managed by the new cache API, as cache changes will affect how the VFS layer handles the target, but won't necessarily propagate to user space immediately. In practical terms, the new APIs improve performance and correctness, but there may still be "cosmetic" issues not being aware anything has changed.
There is already a bug (r.177724575) asking us to support change notifications ("vnode_notify"), so this is definitely an issue we're aware of.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware
