public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/9] Parameter cleanups in extent state helpers
Date: Thu, 25 May 2023 01:04:19 +0200	[thread overview]
Message-ID: <cover.1684967923.git.dsterba@suse.com> (raw)

This is motivated by the gfp parameter passed to all the helpers and how
to get rid of it. Most of the values are GFP_NOFS with some exceptions.
One of them (GFP_NOFAIL) can be removed the other one (GFP_NOWAIT) is
transformed to existing parameters.

Module code size is lower for the whole series and stack is reduced in
about 50 functions by 8 bytes.

David Sterba (9):
  btrfs: open code set_extent_defrag
  btrfs: open code set_extent_delalloc
  btrfs: open code set_extent_new
  btrfs: open code set_extent_dirty
  btrfs: open code set_extent_bits_nowait
  btrfs: open code set_extent_bits
  btrfs: drop NOFAIL from set_extent_bit allocation masks
  btrfs: pass NOWAIT for set/clear extent bits as another bit
  btrfs: drop gfp from parameter extent state helpers

 fs/btrfs/block-group.c           |  6 ++--
 fs/btrfs/defrag.c                |  3 +-
 fs/btrfs/dev-replace.c           |  4 +--
 fs/btrfs/extent-io-tree.c        | 37 ++++++++++++-------
 fs/btrfs/extent-io-tree.h        | 62 ++++++++------------------------
 fs/btrfs/extent-tree.c           | 27 +++++++-------
 fs/btrfs/extent_io.c             |  3 +-
 fs/btrfs/extent_map.c            | 10 +++---
 fs/btrfs/file-item.c             | 10 +++---
 fs/btrfs/inode.c                 |  9 +++--
 fs/btrfs/relocation.c            | 10 +++---
 fs/btrfs/tests/extent-io-tests.c | 16 ++++-----
 fs/btrfs/zoned.c                 |  4 +--
 13 files changed, 91 insertions(+), 110 deletions(-)

-- 
2.40.0


             reply	other threads:[~2023-05-24 23:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 23:04 David Sterba [this message]
2023-05-24 23:04 ` [PATCH 1/9] btrfs: open code set_extent_defrag David Sterba
2023-05-25  8:58   ` Christoph Hellwig
2023-05-25 10:31   ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 2/9] btrfs: open code set_extent_delalloc David Sterba
2023-05-25  8:59   ` Christoph Hellwig
2023-05-25 10:31   ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 3/9] btrfs: open code set_extent_new David Sterba
2023-05-25  8:59   ` Christoph Hellwig
2023-05-25 10:32   ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 4/9] btrfs: open code set_extent_dirty David Sterba
2023-05-25  9:00   ` Christoph Hellwig
2023-05-25 10:33   ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 5/9] btrfs: open code set_extent_bits_nowait David Sterba
2023-05-25  9:02   ` Christoph Hellwig
2023-05-25 22:45     ` David Sterba
2023-05-25 10:33   ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 6/9] btrfs: open code set_extent_bits David Sterba
2023-05-25  9:03   ` Christoph Hellwig
2023-05-25 10:34   ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 7/9] btrfs: drop NOFAIL from set_extent_bit allocation masks David Sterba
2023-05-25  9:06   ` Christoph Hellwig
2023-05-25 23:25     ` David Sterba
2023-05-25 10:38   ` Qu Wenruo
2023-05-25 23:00     ` David Sterba
2023-05-25 23:26       ` Qu Wenruo
2023-05-24 23:04 ` [PATCH 8/9] btrfs: pass NOWAIT for set/clear extent bits as another bit David Sterba
2023-05-24 23:04 ` [PATCH 9/9] btrfs: drop gfp from parameter extent state helpers David Sterba
2023-05-25 10:25 ` [PATCH 0/9] Parameter cleanups in " 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=cover.1684967923.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox