Message ID | 20231107025423.302404-1-xiubli@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | ceph: allocate a smaller extent map if possible | expand |
On Tue, Nov 7, 2023 at 8:26 AM <xiubli@redhat.com> wrote: > > From: Xiubo Li <xiubli@redhat.com> > > For fscrypt case mostly we can predict the max count of the extent > map, so try to allocate a smaller size instead. > > > Xiubo Li (2): > libceph: specify the sparse read extent count > ceph: try to allocate a smaller extent map for sparse read > > fs/ceph/addr.c | 4 +++- > fs/ceph/file.c | 8 ++++++-- > fs/ceph/super.h | 14 ++++++++++++++ > include/linux/ceph/osd_client.h | 6 ++++-- > 4 files changed, 27 insertions(+), 5 deletions(-) > > -- > 2.41.0 > Tested-by: Venky Shankar <vshankar@redhat.com>
From: Xiubo Li <xiubli@redhat.com> For fscrypt case mostly we can predict the max count of the extent map, so try to allocate a smaller size instead. Xiubo Li (2): libceph: specify the sparse read extent count ceph: try to allocate a smaller extent map for sparse read fs/ceph/addr.c | 4 +++- fs/ceph/file.c | 8 ++++++-- fs/ceph/super.h | 14 ++++++++++++++ include/linux/ceph/osd_client.h | 6 ++++-- 4 files changed, 27 insertions(+), 5 deletions(-)