From: Matthew Wilcox <willy@infradead.org>
To: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mcgrof@kernel.org, gost.dev@samsung.com,
akpm@linux-foundation.org, Christian Brauner <brauner@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH 0/2] add block size > page size support to ramfs
Date: Tue, 24 Sep 2024 21:00:26 +0100 [thread overview]
Message-ID: <ZvMaWrXkgZ9ZHKfS@casper.infradead.org> (raw)
In-Reply-To: <20240924192351.74728-1-kernel@pankajraghav.com>
On Tue, Sep 24, 2024 at 09:23:49PM +0200, Pankaj Raghav (Samsung) wrote:
> Add block size > page size to ramfs as we support minimum folio order
> allocation in the page cache. The changes are very minimal, and this is
> also a nice way to stress test just the page cache changes for minimum
> folio order.
I don't really see the point of upstreaming this. I'm sure it was
useful for your testing. And splitting the patch in two makes no sense
to me; the combined patch is not large.
> Pankaj Raghav (2):
> ramfs: add blocksize mount option
> ramfs: enable block size > page size
>
> fs/ramfs/inode.c | 27 +++++++++++++++++++++++++--
> 1 file changed, 25 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2024-09-24 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 19:23 Pankaj Raghav (Samsung)
2024-09-24 19:23 ` [PATCH 1/2] ramfs: add blocksize mount option Pankaj Raghav (Samsung)
2024-09-24 19:23 ` [PATCH 2/2] ramfs: enable block size > page size Pankaj Raghav (Samsung)
2024-09-24 20:00 ` Matthew Wilcox [this message]
2024-09-24 20:24 ` [PATCH 0/2] add block size > page size support to ramfs Pankaj Raghav
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=ZvMaWrXkgZ9ZHKfS@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=gost.dev@samsung.com \
--cc=kernel@pankajraghav.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
/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®