diff options
| author | Yue Hu <[email protected]> | 2022-04-07 19:02:39 +0800 |
|---|---|---|
| committer | David Howells <[email protected]> | 2022-04-08 23:54:37 +0100 |
| commit | 5d3d5b9645b53691b2eee7607cf995bcfae46dd0 (patch) | |
| tree | c414cce000cb8b07324780ddd04ce74a824ae1da | |
| parent | c54eead2a66914a36b4a9ea5bbeb95a768307cba (diff) | |
docs: filesystems: caching/backend-api.rst: fix an object withdrawn API
There's no fscache_are_objects_withdrawn() helper at all to test if
cookie withdrawal is completed currently. The cache backend is using
fscache_wait_for_objects() to wait all objects to be withdrawn.
Signed-off-by: Yue Hu <[email protected]>
Signed-off-by: David Howells <[email protected]>
cc: [email protected]
Link: https://listman.redhat.com/archives/linux-cachefs/2022-April/006705.html # v1
| -rw-r--r-- | Documentation/filesystems/caching/backend-api.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/filesystems/caching/backend-api.rst b/Documentation/filesystems/caching/backend-api.rst index d7b2df5fd607..d7507becf674 100644 --- a/Documentation/filesystems/caching/backend-api.rst +++ b/Documentation/filesystems/caching/backend-api.rst @@ -110,9 +110,9 @@ to withdraw them, calling:: on the cookie that each object belongs to. This schedules the specified cookie for withdrawal. This gets offloaded to a workqueue. The cache backend can -test for completion by calling:: +wait for completion by calling:: - bool fscache_are_objects_withdrawn(struct fscache_cookie *cache); + void fscache_wait_for_objects(struct fscache_cache *cache); Once all the cookies are withdrawn, a cache backend can withdraw all the volumes, calling:: |