From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Pankaj Raghav <p.raghav@samsung.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mcgrof@kernel.org
Subject: Re: [PATCH] mm/filemap: allocate folios according to the blocksize
Date: Sun, 16 Apr 2023 23:27:00 -0700 [thread overview]
Message-ID: <ZDzmtK64elHn6yPg@infradead.org> (raw)
In-Reply-To: <df36a72c-5b20-f071-ec1c-312f43939ebc@suse.de>
On Mon, Apr 17, 2023 at 08:08:04AM +0200, Hannes Reinecke wrote:
> On 4/17/23 06:36, Christoph Hellwig wrote:
> > On Fri, Apr 14, 2023 at 03:49:08PM +0200, Hannes Reinecke wrote:
> > > If the blocksize is larger than the pagesize allocate folios
> > > with the correct order.
> >
> > And how is that supposed to actually happen?
>
> By using my patcheset to brd and set the logical blocksize to eg 16k.
Then add it to your patchset instead of trying to add dead code to the
kernel while also losing context.
next prev parent reply other threads:[~2023-04-17 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230414134914eucas1p1f0b08409dce8bc946057d0a4fa7f1601@eucas1p1.samsung.com>
2023-04-14 13:49 ` [PATCH] mm/filemap: allocate folios according to the blocksize Hannes Reinecke
2023-04-14 13:56 ` Matthew Wilcox
2023-04-16 4:00 ` Matthew Wilcox
2023-04-17 2:18 ` kernel test robot
2023-04-17 4:10 ` Matthew Wilcox
2023-04-17 4:36 ` Christoph Hellwig
2023-04-17 6:08 ` Hannes Reinecke
2023-04-17 6:27 ` Christoph Hellwig [this message]
2023-04-17 6:30 ` Hannes Reinecke
2023-04-20 12:05 ` Pankaj Raghav
2023-04-20 12:19 ` Hannes Reinecke
2023-04-20 12:28 ` Pankaj Raghav
2023-04-20 15:03 ` Darrick J. Wong
2023-04-22 0:14 ` 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=ZDzmtK64elHn6yPg@infradead.org \
--to=hch@infradead.org \
--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=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).