Jeffle Xu <jefflexu@xxxxxxxxxxxxxxxxx> wrote: > Thus simplify the logic of placing backing files, in which backing files > are under "cache/<volume>/" directory directly. You then have a scalability issue on the directory inode lock - and there may also be limits on the capacity of a directory. The hash function is meant to work the same, no matter the cpu arch, so you should be able to copy that to userspace and derive the hash yourself. > Also skip coherency checking currently to ease the development and debug. Better if you can do that in erofs rather than cachefiles. Just set your coherency data to all zeros or something. David
