Messages in this thread | | | From | Jingbo Xu <> | Subject | [PATCH v4 0/2] erofs: support large folios for fscache mode | Date | Thu, 1 Dec 2022 15:42:54 +0800 |
| |
v4: - patch 1: move the change to the INLINE routine to a separate patch which will be sent laterly - patch 1: introduce erofs_fscache_req_chain() helper to improve the code organization - patch 1: misc improvement to make the code cleaner - patch 2: also document the new feature in documentation
v3: https://lore.kernel.org/all/20221129115833.41062-1-jefflexu@linux.alibaba.com/ v2: https://lore.kernel.org/all/20221128025011.36352-1-jefflexu@linux.alibaba.com/ v1: https://lore.kernel.org/all/20221126005756.7662-1-jefflexu@linux.alibaba.com/
v3: - patch 1: when large folios supported, one folio or folio range can be mapped into several slices, with each slice mapped to different cookies, and thus each slice needs its own netfs_cache_resources.
In the implementation of v2, each .read_folio() or .readahead() calling corresponds to only one request, and thus only one netfs_cache_resources (embedded in the request). In this case, fscache_begin_read_operation() may be called multiple times on this cres, while cres->ops->end_operation() is called only once when the whole request completes. This can cause the leakage of the corresponding cachefiles_object->n_accesses refcount, which will cause the user daemon hangs there forever waiting for cache->object_count decreasing to 0 when the user daemon exits.
Worsely, as we mentioned previously, when large folios supported, one folio or folio range can be mapped to multiple chunks on different cookies, in which case each mapped chunk needs its own cres. In the implementation of v2, each .read_folio() or .readahead() calling corresponds to only one request, and thus only one cres. This will make the only cres used by the first chunk gets overridden by the following chunk.
To fix this, we introduce listed requests, where each .read_folio() or .readahead() calling can correspond to a list of requests, with each request corresponds to one cres.
v2: - patch 2: keep the enabling for iomap and fscache mode in separate patches; don't enable the feature for the meta data routine for now (Gao Xiang)
Patch 1 is the main part of supporting large folios for fscache mode. It relies on a pending patch[1] adding .prepare_ondemand_read() interface in Cachefiles.
Patch 2 just turns the switch on and enables the feature for fscache mode. It relies on a previous patch[2] which enables this feature for iomap mode.
[1] https://lore.kernel.org/all/20221124034212.81892-1-jefflexu@linux.alibaba.com/ [2] https://lore.kernel.org/all/20221110074023.8059-1-jefflexu@linux.alibaba.com/
Jingbo Xu (2): erofs: support large folios for fscache mode erofs: enable large folios for fscache mode
Documentation/filesystems/erofs.rst | 2 + fs/erofs/fscache.c | 148 +++++++++++++++------------- fs/erofs/inode.c | 3 +- 3 files changed, 83 insertions(+), 70 deletions(-)
-- 2.19.1.6.gb485710b
| |