Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: cleanup on the extra_gfp parameters
Date: Thu, 27 Jun 2024 14:01:58 +0930	[thread overview]
Message-ID: <cover.1719462554.git.wqu@suse.com> (raw)

The @extra_gfp parameters for page/folio array allocation is only for
extent buffer allocation to pass __GFP_NOFAIL.

Meanwhile all the callers have to pay for the extra parameter.

This patchset removes the parameter, and introduce an internal version
of btrfs_alloc_page_array() to handle the __GFP_NOFAIL case.
Furthermore, for that internal version, use a bool to indicate wheter
it's a NOFAIL allocation or not.

Qu Wenruo (2):
  btrfs: remove the extra_gfp parameter from btrfs_alloc_folio_array()
  btrfs: remove the extra_gfp parameter from btrfs_alloc_page_array()

 fs/btrfs/compression.c |  2 +-
 fs/btrfs/extent_io.c   | 51 +++++++++++++++++++++---------------------
 fs/btrfs/extent_io.h   |  6 ++---
 fs/btrfs/inode.c       |  2 +-
 fs/btrfs/raid56.c      |  6 ++---
 fs/btrfs/scrub.c       |  2 +-
 6 files changed, 34 insertions(+), 35 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-06-27  4:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  4:31 Qu Wenruo [this message]
2024-06-27  4:31 ` [PATCH 1/2] btrfs: remove the extra_gfp parameter from btrfs_alloc_folio_array() Qu Wenruo
2024-06-27  8:51   ` Filipe Manana
2024-06-27  4:32 ` [PATCH 2/2] btrfs: remove the extra_gfp parameter from btrfs_alloc_page_array() Qu Wenruo
2024-06-27  8:50   ` Filipe Manana
2024-06-27 10:15     ` Qu Wenruo
2024-06-27 10:38       ` Filipe Manana
2024-06-27 10:40         ` 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.1719462554.git.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