public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Pankaj Raghav <p.raghav@samsung.com>
Cc: brauner@kernel.org, viro@zeniv.linux.org.uk,
	akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, mcgrof@kernel.org,
	gost.dev@samsung.com, hare@suse.de
Subject: Re: [RFC 2/4] buffer: add alloc_folio_buffers() helper
Date: Fri, 14 Apr 2023 14:06:33 +0100	[thread overview]
Message-ID: <ZDlP2fevtfD5gMPd@casper.infradead.org> (raw)
In-Reply-To: <20230414110821.21548-3-p.raghav@samsung.com>

On Fri, Apr 14, 2023 at 01:08:19PM +0200, Pankaj Raghav wrote:
> Folio version of alloc_page_buffers() helper. This is required to convert
> create_page_buffers() to create_folio_buffers() later in the series.
> 
> It removes one call to compound_head() compared to alloc_page_buffers().

I would convert alloc_page_buffers() to folio_alloc_buffers() and
add

static struct buffer_head *alloc_page_buffers(struct page *page,
		unsigned long size, bool retry)
{
	return folio_alloc_buffers(page_folio(page), size, retry);
}

in buffer_head.h

(there are only five callers, so this feels like a better tradeoff
than creating a new function)

> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
>  fs/buffer.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 59 insertions(+)
> 
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 44380ff3a31f..0f9c2127543d 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -900,6 +900,65 @@ struct buffer_head *alloc_page_buffers(struct page *page, unsigned long size,
>  }
>  EXPORT_SYMBOL_GPL(alloc_page_buffers);
>  
> +/*
> + * Create the appropriate buffers when given a folio for data area and
> + * the size of each buffer.. Use the bh->b_this_page linked list to
> + * follow the buffers created.  Return NULL if unable to create more
> + * buffers.
> + *
> + * The retry flag is used to differentiate async IO (paging, swapping)
> + * which may not fail from ordinary buffer allocations.
> + */
> +struct buffer_head *alloc_folio_buffers(struct folio *folio, unsigned long size,
> +					bool retry)
> +{
> +	struct buffer_head *bh, *head;
> +	gfp_t gfp = GFP_NOFS | __GFP_ACCOUNT;
> +	long offset;
> +	struct mem_cgroup *memcg, *old_memcg;
> +
> +	if (retry)
> +		gfp |= __GFP_NOFAIL;
> +
> +	/* The folio lock pins the memcg */
> +	memcg = folio_memcg(folio);
> +	old_memcg = set_active_memcg(memcg);
> +
> +	head = NULL;
> +	offset = folio_size(folio);
> +	while ((offset -= size) >= 0) {
> +		bh = alloc_buffer_head(gfp);
> +		if (!bh)
> +			goto no_grow;
> +
> +		bh->b_this_page = head;
> +		bh->b_blocknr = -1;
> +		head = bh;
> +
> +		bh->b_size = size;
> +
> +		/* Link the buffer to its folio */
> +		set_bh_folio(bh, folio, offset);
> +	}
> +out:
> +	set_active_memcg(old_memcg);
> +	return head;
> +/*
> + * In case anything failed, we just free everything we got.
> + */
> +no_grow:
> +	if (head) {
> +		do {
> +			bh = head;
> +			head = head->b_this_page;
> +			free_buffer_head(bh);
> +		} while (head);
> +	}
> +
> +	goto out;
> +}
> +EXPORT_SYMBOL_GPL(alloc_folio_buffers);
> +
>  static inline void
>  link_dev_buffers(struct page *page, struct buffer_head *head)
>  {
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-04-14 13:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230414110825eucas1p1ed4d16627889ef8542dfa31b1183063d@eucas1p1.samsung.com>
2023-04-14 11:08 ` [RFC 0/4] convert create_page_buffers to create_folio_buffers Pankaj Raghav
2023-04-14 11:08   ` [RFC 1/4] fs/buffer: add set_bh_folio helper Pankaj Raghav
2023-04-14 11:08   ` [RFC 2/4] buffer: add alloc_folio_buffers() helper Pankaj Raghav
2023-04-14 13:06     ` Matthew Wilcox [this message]
2023-04-14 15:01       ` Pankaj Raghav
2023-04-14 11:08   ` [RFC 3/4] fs/buffer: add folio_create_empty_buffers helper Pankaj Raghav
2023-04-14 13:16     ` Matthew Wilcox
2023-04-14 11:08   ` [RFC 4/4] fs/buffer: convert create_page_buffers to create_folio_buffers Pankaj Raghav
2023-04-14 13:21     ` Matthew Wilcox
2023-04-14 13:47   ` [RFC 0/4] " Hannes Reinecke
2023-04-14 13:51     ` Matthew Wilcox
2023-04-14 13:56       ` Hannes Reinecke
2023-04-14 15:00     ` Pankaj Raghav
2023-04-15  1:01     ` Luis Chamberlain
2023-04-15  2:31       ` Matthew Wilcox
2023-04-15  3:24         ` Luis Chamberlain
2023-04-15  3:44           ` Matthew Wilcox
2023-04-15 13:14             ` Hannes Reinecke
2023-04-15 17:09               ` Matthew Wilcox
2023-04-16  1:28                 ` Luis Chamberlain
2023-04-16  3:40                   ` Matthew Wilcox
2023-04-16  5:26                     ` Luis Chamberlain
2023-04-16 14:07                       ` Matthew Wilcox
2023-04-17 15:40                         ` Darrick J. Wong
2023-04-16 22:57                       ` Dave Chinner
2023-04-17  2:27     ` Luis Chamberlain
2023-04-17  6:04       ` Hannes Reinecke

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=ZDlP2fevtfD5gMPd@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=hare@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=viro@zeniv.linux.org.uk \
    /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