virtio-fs: Get rid of inode lock and misc fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | fuse: Continue to wait if inline reclaim returns nullfs/ | +5 | 0 replies | |
| 2/6 | fuse: Requeue work if number of free ranges is not above thresholdfs/ | +31 | 0 replies | |
| 3/6 | fuse: Do cond_resched() if we can't get inode lockfs/ | +2 | 0 replies | |
| 4/6 | fuse: Get rid of inode lock in range reclaim pathfs/ fs/ fs/ | +42 | 0 replies | |
| 5/6 | fuse: Get rid of -EAGAIN logic in dmap free worker threadfs/ | +1 | 0 replies | |
| 6/6 | fuse: Dax read can now do range reclaim inlinefs/ | +13 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Virtio-fs] [PATCH 0/6] virtio-fs: Get rid of inode lock and misc fixes
Hi Liu Bo,
I am proposing following patches and fixes. I have modified your patch a bit to use refcount_t.
I have done few other cleanup and fixes as well.
If things look good, I will squash these patches into exisitng patches.
Thanks
Vivek
Vivek Goyal (6):
fuse: Continue to wait if inline reclaim returns null
fuse: Requeue work if number of free ranges is not above threshold
fuse: Do cond_resched() if we can't get inode lock
fuse: Get rid of inode lock in range reclaim path
fuse: Get rid of -EAGAIN logic in dmap free worker thread
fuse: Dax read can now do range reclaim inline
fs/fuse/file.c | 161 ++++++++++++++++++++++++++--------------------- fs/fuse/fuse_i.h | 3 + fs/fuse/inode.c | 1 + 3 files changed, 93 insertions(+), 72 deletions(-)
Signature · 1 line
2.20.1