On 12/10/21 7:04 PM, David Howells wrote: > 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. Yes, as described in the cover letter, I plan to make the hashing algorithm used by cachefiles built-in into our user daemon, so that the user daemon could place the blob file on the right place. Then the core logic of cachefiles won't be touched as much as possible. > >> 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. > Yes it is preferred to keep the general part of cachefiles untouched. Later we can set "CacheFiles.cache" xattr on blob files in advance to pass this check. -- Thanks, Jeffle -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/linux-cachefs
