From: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Nick Terrell <terrelln@fb.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
kernel-team@fb.com
Cc: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [PATCH v2 0/2] btrfs: allocate page arrays more efficiently
Date: Wed, 30 Mar 2022 12:44:05 -0400 [thread overview]
Message-ID: <cover.1648658235.git.sweettea-kernel@dorminy.me> (raw)
In several places, btrfs allocates an array of pages, one at a time. In
addition to duplicating code, the mm subsystem provides a helper to
allocate multiple pages at once into an array which is suited for our
usecase. In the fast path, the batching can result in better allocation
decisions and less locking. This changeset first adjusts the users to
call a common array-of-pages allocation function, then adjusts that
common function to use the batch page allocator.
v2: moved new helper to extent_io.[ch]. Fixed title format.
v1: https://lore.kernel.org/linux-btrfs/cover.1648496453.git.sweettea-kernel@dorminy.me/
Sweet Tea Dorminy (2):
btrfs: factor out allocating an array of pages
btrfs: allocate page arrays using bulk page allocator
fs/btrfs/check-integrity.c | 8 ++---
fs/btrfs/compression.c | 37 +++++++++-----------
fs/btrfs/extent_io.c | 72 +++++++++++++++++++++++++++++---------
fs/btrfs/extent_io.h | 2 ++
fs/btrfs/inode.c | 10 +++---
fs/btrfs/raid56.c | 30 +++-------------
6 files changed, 85 insertions(+), 74 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-30 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 16:44 Sweet Tea Dorminy [this message]
2022-03-30 16:44 ` [PATCH v2 1/2] btrfs: factor out allocating an array of pages Sweet Tea Dorminy
2022-03-30 16:44 ` [PATCH v2 2/2] btrfs: allocate page arrays using bulk page allocator Sweet Tea Dorminy
2022-03-30 16:58 ` [PATCH v2 0/2] btrfs: allocate page arrays more efficiently David Sterba
2022-03-30 18:08 ` Sweet Tea Dorminy
2022-03-31 16:43 ` David Sterba
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=cover.1648658235.git.sweettea-kernel@dorminy.me \
--to=sweettea-kernel@dorminy.me \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.