From: Matthew Wilcox <willy@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/5] brd: convert to folios
Date: Tue, 21 Mar 2023 15:00:03 +0000 [thread overview]
Message-ID: <ZBnGc4WbBOlnRUgd@casper.infradead.org> (raw)
In-Reply-To: <a4489f7b-912c-e68f-4a4c-c14d96026bd6@suse.de>
On Tue, Mar 07, 2023 at 09:14:27AM +0100, Hannes Reinecke wrote:
> On 3/7/23 08:30, Matthew Wilcox wrote:
> > On Tue, Mar 07, 2023 at 07:55:32AM +0100, Hannes Reinecke wrote:
> > > On 3/6/23 18:37, Matthew Wilcox wrote:
> > > > On Mon, Mar 06, 2023 at 01:01:23PM +0100, Hannes Reinecke wrote:
> > > > > - page = alloc_page(gfp | __GFP_ZERO | __GFP_HIGHMEM);
> > > > > - if (!page)
> > > > > + folio = folio_alloc(gfp | __GFP_ZERO, 0);
> > > > > + if (!folio)
> > > >
> > > > Did you drop HIGHMEM support on purpose?
> > >
> > > No; I thought that folios would be doing that implicitely.
> > > Will be re-adding.
> >
> > We can't ... not all filesystems want to allocate every folio from
> > HIGHMEM. eg for superblocks, it often makes more sense to allocate the
> > folio from lowmem than allocate it from highmem and keep it kmapped.
> > The only GFP flag that folios force-set is __GFP_COMP because folios by
> > definition are compound pages.
>
> Oh well.
>
> However, when playing with the modified brd and setting the logical&physical
> blocksize to 16k the whole thing crashes
> (not unexpectedly).
> It does crash, however, in block_read_full_folio(), which rather
> surprisingly (at least for me) is using create_page_buffers();
> I would have expected something like create_folio_buffers().
> Is this work in progress or what is the plan here?
Supporting folios > PAGE_SIZE in blockdev is definitely still WIP.
I know of at least one bug, which is:
#define bh_offset(bh) ((unsigned long)(bh)->b_data & ~PAGE_MASK)
That needs to be something like
static size_t bh_offset(const struct buffer_head *bh)
{
return (unsigned long)bh->b_data & (folio_size(bh->b_folio) - 1);
}
I haven't done a thorough scan for folio-size problems in the block
layer; I've just been fixing up things as I notice them.
Yes, create_page_buffers() should now be create_folio_buffers(). Just
didn't get round to it yet.
next parent reply other threads:[~2023-03-21 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230306120127.21375-1-hare@suse.de>
[not found] ` <20230306120127.21375-2-hare@suse.de>
[not found] ` <ZAYk5wOUaXAIouQ5@casper.infradead.org>
[not found] ` <76613838-fa4c-7f3e-3417-7a803fafc6c2@suse.de>
[not found] ` <ZAboHUp/YUkEs/D1@casper.infradead.org>
[not found] ` <a4489f7b-912c-e68f-4a4c-c14d96026bd6@suse.de>
2023-03-21 15:00 ` Matthew Wilcox [this message]
2023-03-21 15:26 ` [PATCH 1/5] brd: convert to folios 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=ZBnGc4WbBOlnRUgd@casper.infradead.org \
--to=willy@infradead.org \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).