[RFC 02/19] cachefiles: implement key scheme for demand-read mode

David Howells dhowells at redhat.com
Fri Dec 10 22:04:53 AEDT 2021


Jeffle Xu <jefflexu at linux.alibaba.com> 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



More information about the Linux-erofs mailing list