From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 03/19] btrfs: calculate inline extent buffer page size based on page size
Date: Tue, 15 Sep 2020 13:35:16 +0800 [thread overview]
Message-ID: <20200915053532.63279-4-wqu@suse.com> (raw)
In-Reply-To: <20200915053532.63279-1-wqu@suse.com>
Btrfs only support 64K as max node size, thus for 4K page system, we
would have at most 16 pages for one extent buffer.
For a system using 64K page size, we would really have just one
single page.
While we always use 16 pages for extent_buffer::pages[], this means for
systems using 64K pages, we are wasting memory for the 15 pages which
will never be utilized.
So this patch will change how the extent_buffer::pages[] array size is
calclulated, now it will be calculated using
BTRFS_MAX_METADATA_BLOCKSIZE and PAGE_SIZE.
For systems using 4K page size, it will stay 16 pages.
For systems using 64K page size, it will be just 1 page.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
fs/btrfs/extent_io.c | 6 +++---
fs/btrfs/extent_io.h | 8 +++++---
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index 6def411b2eba..674d3b82751f 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -5004,9 +5004,9 @@ __alloc_extent_buffer(struct btrfs_fs_info *fs_info, u64 start,
/*
* Sanity checks, currently the maximum is 64k covered by 16x 4k pages
*/
- BUILD_BUG_ON(BTRFS_MAX_METADATA_BLOCKSIZE
- > MAX_INLINE_EXTENT_BUFFER_SIZE);
- BUG_ON(len > MAX_INLINE_EXTENT_BUFFER_SIZE);
+ BUILD_BUG_ON(BTRFS_MAX_METADATA_BLOCKSIZE >
+ INLINE_EXTENT_BUFFER_PAGES * PAGE_SIZE);
+ BUG_ON(len > BTRFS_MAX_METADATA_BLOCKSIZE);
#ifdef CONFIG_BTRFS_DEBUG
eb->spinning_writers = 0;
diff --git a/fs/btrfs/extent_io.h b/fs/btrfs/extent_io.h
index 00a88f2eb5ab..d511890702cc 100644
--- a/fs/btrfs/extent_io.h
+++ b/fs/btrfs/extent_io.h
@@ -85,9 +85,11 @@ struct extent_io_ops {
int mirror);
};
-
-#define INLINE_EXTENT_BUFFER_PAGES 16
-#define MAX_INLINE_EXTENT_BUFFER_SIZE (INLINE_EXTENT_BUFFER_PAGES * PAGE_SIZE)
+/*
+ * The SZ_64K is BTRFS_MAX_METADATA_BLOCKSIZE, here just to avoid circle
+ * including "ctree.h".
+ */
+#define INLINE_EXTENT_BUFFER_PAGES (SZ_64K / PAGE_SIZE)
struct extent_buffer {
u64 start;
unsigned long len;
--
2.28.0
next prev parent reply other threads:[~2020-09-15 5:35 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 5:35 [PATCH v2 00/19] btrfs: add read-only support for subpage sector size Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 01/19] btrfs: extent-io-tests: remove invalid tests Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 02/19] btrfs: remove the unnecessary parameter @start and @len for check_data_csum() Qu Wenruo
2020-09-15 8:39 ` Johannes Thumshirn
2020-09-15 5:35 ` Qu Wenruo [this message]
2020-09-15 8:35 ` [PATCH v2 03/19] btrfs: calculate inline extent buffer page size based on page size Nikolay Borisov
2020-09-15 10:05 ` Qu Wenruo
2020-09-15 8:40 ` Johannes Thumshirn
2020-09-15 5:35 ` [PATCH v2 04/19] btrfs: remove the open-code to read disk-key Qu Wenruo
2020-09-15 8:36 ` Nikolay Borisov
2020-09-15 8:40 ` Johannes Thumshirn
2020-09-16 16:01 ` David Sterba
2020-09-17 8:02 ` Qu Wenruo
2020-09-17 12:37 ` David Sterba
2020-09-17 13:15 ` Qu Wenruo
2020-09-17 22:41 ` David Sterba
2020-09-17 23:26 ` Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 05/19] btrfs: make btrfs_fs_info::buffer_radix to take sector size devided values Qu Wenruo
2020-09-15 8:27 ` Johannes Thumshirn
2020-09-15 10:04 ` Qu Wenruo
2020-09-15 10:12 ` Johannes Thumshirn
2020-09-15 17:40 ` kernel test robot
2020-09-15 5:35 ` [PATCH v2 06/19] btrfs: don't allow tree block to cross page boundary for subpage support Qu Wenruo
2020-09-15 8:37 ` Nikolay Borisov
2020-09-15 10:06 ` Qu Wenruo
2020-09-15 8:44 ` Johannes Thumshirn
2020-09-15 5:35 ` [PATCH v2 07/19] btrfs: update num_extent_pages() to support subpage sized extent buffer Qu Wenruo
2020-09-15 8:42 ` Johannes Thumshirn
2020-09-15 10:07 ` Qu Wenruo
2020-09-15 10:12 ` Johannes Thumshirn
2020-09-15 10:07 ` Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 08/19] btrfs: handle sectorsize < PAGE_SIZE case for extent buffer accessors Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 09/19] btrfs: make csum_tree_block() handle sectorsize smaller than page size Qu Wenruo
2020-09-15 8:47 ` Johannes Thumshirn
2020-09-15 5:35 ` [PATCH v2 10/19] btrfs: add assert_spin_locked() for attach_extent_buffer_page() Qu Wenruo
2020-09-15 8:52 ` Johannes Thumshirn
2020-09-15 5:35 ` [PATCH v2 11/19] btrfs: extract the extent buffer verification from btree_readpage_end_io_hook() Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 12/19] btrfs: extent_io: only require sector size alignment for page read Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 13/19] btrfs: make btrfs_readpage_end_io_hook() follow sector size Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 14/19] btrfs: make btree inode io_tree has its special owner Qu Wenruo
2020-09-16 9:28 ` Johannes Thumshirn
2020-09-16 16:06 ` David Sterba
2020-09-17 0:02 ` Qu Wenruo
2020-09-17 12:50 ` David Sterba
2020-09-18 8:18 ` Qu Wenruo
2020-09-22 14:06 ` David Sterba
2020-09-22 14:14 ` David Sterba
2020-09-15 5:35 ` [PATCH v2 15/19] btrfs: don't set extent_io_tree bits for btree inode at endio time Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 16/19] btrfs: use extent_io_tree to handle subpage extent buffer allocation Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 17/19] btrfs: implement subpage metadata read and its endio function Qu Wenruo
2020-09-16 8:47 ` kernel test robot
2020-09-15 5:35 ` [PATCH v2 18/19] btrfs: implement btree_readpage() and try_release_extent_buffer() for subpage Qu Wenruo
2020-09-15 5:35 ` [PATCH v2 19/19] btrfs: allow RO mount of 4K sector size fs on 64K page system Qu Wenruo
2020-09-16 1:35 ` [PATCH v2 00/19] btrfs: add read-only support for subpage sector size Qu Wenruo
2020-09-16 16:18 ` Neal Gompa
2020-09-17 0:03 ` Qu Wenruo
2020-09-17 0:13 ` Neal Gompa
2020-09-17 0:24 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915053532.63279-4-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).