From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/5] Siwtch to on-stack variables for block reserves
Date: Fri, 22 Sep 2023 21:10:22 +0200 [thread overview]
Message-ID: <cover.1695408280.git.dsterba@suse.com> (raw)
The block reserve structure is small enough to fit on stack so do that
in a few functions and avoid allocation. This in turn allows to remove
the alloc/free wrappers.
David Sterba (5):
btrfs: use on-stack variable for block reserve in btrfs_evict_inode
btrfs: use on-stack variable for block reserve in btrfs_truncate
btrfs: use on-stack variable for block reserve in btrfs_replace_file_extents
btrfs: relocation: embed block reserve to struct reloc_control
btrfs: remove unused alloc and free helpers for block group reserves
fs/btrfs/block-rsv.c | 22 --------------------
fs/btrfs/block-rsv.h | 4 ----
fs/btrfs/file.c | 29 +++++++++++---------------
fs/btrfs/inode.c | 47 ++++++++++++++++++++-----------------------
fs/btrfs/relocation.c | 46 +++++++++++++++++++-----------------------
5 files changed, 55 insertions(+), 93 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-22 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 19:10 David Sterba [this message]
2023-09-22 19:10 ` [PATCH 1/5] btrfs: use on-stack variable for block reserve in btrfs_evict_inode David Sterba
2023-09-22 19:10 ` [PATCH 2/5] btrfs: use on-stack variable for block reserve in btrfs_truncate David Sterba
2023-09-22 19:10 ` [PATCH 3/5] btrfs: use on-stack variable for block reserve in btrfs_replace_file_extents David Sterba
2023-09-22 19:10 ` [PATCH 4/5] btrfs: relocation: embed block reserve to struct reloc_control David Sterba
2023-09-22 19:10 ` [PATCH 5/5] btrfs: remove unused alloc and free helpers for block group reserves David Sterba
2023-09-27 14:29 ` [PATCH 0/5] Siwtch to on-stack variables for block reserves 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.1695408280.git.dsterba@suse.com \
--to=dsterba@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 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.