On Thu, 21 Sept 2023 at 11:17, Amir Goldstein <amir73il@xxxxxxxxx> wrote: > I don't mind dropping the "inode bound" patch altogether > and staying with server managed backing_id without support > for auto-close-on-evict and only support per-file-auto-close > as is already implemented in my POC. Lets do that, then. > IWO, if the server want to associate a backing file id with an > inode on LOOKUP or on open, it has no problem is keeping > this association in the server internally, replying to any open > with the backing_id that it associated and closing the > backing_id on FORGET or on the last close. Right. The only gain is when we want to omit the OPEN call. But that's definitely not urgent. > Different FUSE files may have different open flags > (e.g. O_RDONLY/O_RDWR/O_SYNC) so server may want to use > different backing files for different FUSE files on the same inode, > but perhaps this is not what you were asking? Yes, this answers my question. THanks, Miklos
