From: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: willy@infradead.org, mcgrof@kernel.org, gost.dev@samsung.com,
akpm@linux-foundation.org, kernel@pankajraghav.com,
Christian Brauner <brauner@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>
Subject: [PATCH 0/2] add block size > page size support to ramfs
Date: Tue, 24 Sep 2024 21:23:49 +0200 [thread overview]
Message-ID: <20240924192351.74728-1-kernel@pankajraghav.com> (raw)
From: Pankaj Raghav <p.raghav@samsung.com>
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 tested the changes from blocksize 4k to 2M with ltp's fsx on an x86
machine.
I ran a basic perf test with dd as follows:
$ mount ramfs -t ramfs -o blocksize=$bs /media/test/
$ dd if=/mnt/rand of="/media/test/rand" bs=2M count=2048
+------+----------+
| bs | BW(GB/s) |
+------+----------+
| 4k | 1.7 |
| 8k | 2.4 |
| 16k | 3.2 |
| 32k | 4.0 |
| 64k | 4.5 |
| 128k | 4.8 |
| 256k | 5.3 |
| 512k | 5.5 |
| 1M | 5.6 |
| 2M | 5.6 |
+------+----------+
We get better performance for larger bs as we allocate larger folios
instead of multiple smaller folios when there is no memory fragmentation
and pressure.
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(-)
base-commit: 4d0326b60bb753627437fff0f76bf1525bcda422
--
2.44.1
next reply other threads:[~2024-09-24 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 19:23 Pankaj Raghav (Samsung) [this message]
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 ` [PATCH 0/2] add block size > page size support to ramfs Matthew Wilcox
2024-09-24 20:24 ` 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=20240924192351.74728-1-kernel@pankajraghav.com \
--to=kernel@pankajraghav.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=gost.dev@samsung.com \
--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
all inboxes | Powered by JetHome®