From: Pankaj Raghav <p.raghav@samsung.com>
To: Hannes Reinecke <hare@suse.de>, <willy@infradead.org>,
<david@fromorbit.com>
Cc: <gost.dev@samsung.com>, <mcgrof@kernel.org>, <hch@lst.de>,
<jwong@kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC 3/4] block: set mapping order for the block cache in set_init_blocksize
Date: Wed, 21 Jun 2023 14:02:57 +0200 [thread overview]
Message-ID: <e9604e71-bfd4-bf72-cb0b-b3dbcc492c3f@samsung.com> (raw)
In-Reply-To: <58279efe-141b-5d6b-b319-7bd1a0d5347d@suse.de>
>>
>> Hmm, which aops are you using for the block device? If you are using the old aops, then we will be
>> using helpers from buffer.c and mpage.c which do not support large folios. I am getting a BUG_ON
>> when I don't use iomap based aops for the block device:
>>
> I know. I haven't said that mpage.c / buffer.c support large folios _now_. All I'm saying is that I
> have a patchset enabling it to support large folios :-)
>
Ah ok! I thought we are not going that route based on the discussion we had in LSF.
> Cheers,
>
> Hannes
>
next prev parent reply other threads:[~2023-06-21 12:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230621083825eucas1p1b05a6d7e0bf90e7a3d8e621f6578ff0a@eucas1p1.samsung.com>
2023-06-21 8:38 ` [RFC 0/4] minimum folio order support in filemap Pankaj Raghav
[not found] ` <CGME20230621083826eucas1p11fc8d3e023caafa8b30fd04c66c9c7d0@eucas1p1.samsung.com>
2023-06-21 8:38 ` [RFC 1/4] fs: Allow fine-grained control of folio sizes Pankaj Raghav
2023-06-21 9:02 ` Hannes Reinecke
[not found] ` <CGME20230621083827eucas1p2948b4efaf55064c3761c924b5b049219@eucas1p2.samsung.com>
2023-06-21 8:38 ` [RFC 2/4] filemap: use minimum order while allocating folios Pankaj Raghav
2023-06-21 8:59 ` Hannes Reinecke
2023-06-21 10:25 ` Pankaj Raghav
[not found] ` <CGME20230621083828eucas1p23222cae535297f9536f12dddd485f97b@eucas1p2.samsung.com>
2023-06-21 8:38 ` [RFC 3/4] block: set mapping order for the block cache in set_init_blocksize Pankaj Raghav
2023-06-21 9:05 ` Hannes Reinecke
2023-06-21 10:42 ` Pankaj Raghav
2023-06-21 11:02 ` Hannes Reinecke
2023-06-21 12:02 ` Pankaj Raghav [this message]
2023-06-24 8:35 ` kernel test robot
[not found] ` <CGME20230621083830eucas1p1c7e6ea9e23949a9688aac6f9f3ea25fb@eucas1p1.samsung.com>
2023-06-21 8:38 ` [RFC 4/4] nvme: enable logical block size > PAGE_SIZE Pankaj Raghav
2023-06-21 9:07 ` Hannes Reinecke
2023-06-21 10:47 ` Pankaj Raghav
2023-06-21 9:00 ` [RFC 0/4] minimum folio order support in filemap Hannes Reinecke
2023-06-21 22:07 ` Dave Chinner
2023-06-22 5:51 ` Hannes Reinecke
2023-06-22 6:50 ` Hannes Reinecke
2023-06-22 10:20 ` Dave Chinner
2023-06-22 10:23 ` Hannes Reinecke
2023-06-22 22:33 ` Dave Chinner
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=e9604e71-bfd4-bf72-cb0b-b3dbcc492c3f@samsung.com \
--to=p.raghav@samsung.com \
--cc=david@fromorbit.com \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).