From: Pankaj Raghav <p.raghav@samsung.com>
To: 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, hare@suse.de, gost.dev@samsung.com,
Pankaj Raghav <p.raghav@samsung.com>
Subject: [PATCH 0/4] convert create_page_buffers to folio_create_buffers
Date: Mon, 17 Apr 2023 14:36:14 +0200 [thread overview]
Message-ID: <20230417123618.22094-1-p.raghav@samsung.com> (raw)
In-Reply-To: <CGME20230417123620eucas1p229311e1b4c661bd493509135ba748300@eucas1p2.samsung.com>
One of the first kernel panic we hit when we try to increase the
block size > 4k is inside create_page_buffers()[1]. Even though buffer.c
function do not support large folios (folios > PAGE_SIZE) at the moment,
these changes are required when we want to remove that constraint.
Willy had already mentioned that he wanted to convert create_page_buffers to
folio_create_buffers but didn't get to it yet, so I decided to take a
shot.
No functional changes introduced.
Changes since RFC[2]:
- Renaming the helpers with folio_*
- Calling folio_* helper version inside the *page* helper.
[1] https://lore.kernel.org/all/ZBnGc4WbBOlnRUgd@casper.infradead.org/
[2]https://lore.kernel.org/lkml/20230414110821.21548-1-p.raghav@samsung.com/
Pankaj Raghav (4):
fs/buffer: add folio_set_bh helper
buffer: add folio_alloc_buffers() helper
fs/buffer: add folio_create_empty_buffers helper
fs/buffer: convert create_page_buffers to folio_create_buffers
fs/buffer.c | 89 +++++++++++++++++++++++++------------
include/linux/buffer_head.h | 6 +++
2 files changed, 66 insertions(+), 29 deletions(-)
--
2.34.1
next parent reply other threads:[~2023-04-17 12:36 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 ` Pankaj Raghav [this message]
[not found] ` <CGME20230417123620eucas1p266aa61d2213f94bbe028a98be73b70fc@eucas1p2.samsung.com>
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
[not found] ` <CGME20230417123621eucas1p12ef0592f7d9b97bf105ff9990da22a48@eucas1p1.samsung.com>
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
[not found] ` <CGME20230417123621eucas1p23d1669a8b1e27d4dec64626dcb7fbd78@eucas1p2.samsung.com>
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
[not found] ` <CGME20230417123627eucas1p2d3e6824e87d4fdadf459be74845ea0a8@eucas1p2.samsung.com>
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
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=20230417123618.22094-1-p.raghav@samsung.com \
--to=p.raghav@samsung.com \
--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=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
all inboxes | Powered by JetHome®