From: Hannes Reinecke <hare@suse.de>
To: Pankaj Raghav <p.raghav@samsung.com>,
viro@zeniv.linux.org.uk, brauner@kernel.org, willy@infradead.org,
akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, mcgrof@kernel.org,
linux-kernel@vger.kernel.org, gost.dev@samsung.com
Subject: Re: [PATCH 4/4] fs/buffer: convert create_page_buffers to folio_create_buffers
Date: Mon, 17 Apr 2023 16:05:10 +0200 [thread overview]
Message-ID: <24b77b42-0f31-2750-e792-dc80673eb56b@suse.de> (raw)
In-Reply-To: <20230417123618.22094-5-p.raghav@samsung.com>
On 4/17/23 14:36, Pankaj Raghav wrote:
> fs/buffer do not support large folios as there are many assumptions on
> the folio size to be the host page size. This conversion is one step
> towards removing that assumption. Also this conversion will reduce calls
> to compound_head() if folio_create_buffers() calls
> folio_create_empty_buffers().
>
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
> fs/buffer.c | 23 +++++++++++++----------
> 1 file changed, 13 insertions(+), 10 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
prev parent reply other threads:[~2023-04-17 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230417123620eucas1p229311e1b4c661bd493509135ba748300@eucas1p2.samsung.com>
2023-04-17 12:36 ` [PATCH 0/4] convert create_page_buffers to folio_create_buffers Pankaj Raghav
2023-04-17 12:36 ` [PATCH 1/4] fs/buffer: add folio_set_bh helper Pankaj Raghav
2023-04-17 13:24 ` Matthew Wilcox
2023-04-17 14:03 ` Hannes Reinecke
2023-04-17 12:36 ` [PATCH 2/4] buffer: add folio_alloc_buffers() helper Pankaj Raghav
2023-04-17 13:31 ` Matthew Wilcox
2023-04-17 14:03 ` Hannes Reinecke
2023-04-17 12:36 ` [PATCH 3/4] fs/buffer: add folio_create_empty_buffers helper Pankaj Raghav
2023-04-17 13:33 ` Matthew Wilcox
2023-04-17 14:04 ` Hannes Reinecke
2023-04-17 12:36 ` [PATCH 4/4] fs/buffer: convert create_page_buffers to folio_create_buffers Pankaj Raghav
2023-04-17 13:37 ` Matthew Wilcox
2023-04-17 14:05 ` Hannes Reinecke [this message]
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=24b77b42-0f31-2750-e792-dc80673eb56b@suse.de \
--to=hare@suse.de \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=gost.dev@samsung.com \
--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 \
--cc=willy@infradead.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