linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Raghav <p.raghav@samsung.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>,
	<hughd@google.com>, <slava@dubeyko.com>,
	<kirill.shutemov@linux.intel.com>, <mcgrof@kernel.org>,
	<hare@suse.com>, "Darrick J. Wong" <djwong@kernel.org>
Subject: [PATCH] mm: Support order-1 folios in the page cache
Date: Mon, 22 Jan 2024 15:36:19 +0100	[thread overview]
Message-ID: <6b93a509-fbaa-4311-8ee9-fd98e2fd2546@samsung.com> (raw)
In-Reply-To: <CGME20240122143620eucas1p1017072128a3b497fd95b796ebaad71a2@eucas1p1.samsung.com>

> Folios of order 1 have no space to store the deferred list.  This is
> not a problem for the page cache as file-backed folios are never
> placed on the deferred list.  All we need to do is prevent the core
> MM from touching the deferred list for order 1 folios and remove the
> code which prevented us from allocating order 1 folios.
>
> Link: https://lore.kernel.org/linux-mm/90344ea7-4eec-47ee-5996-0c22f42d6a6a@google.com/
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>

This is something I was looking forward to while developing the LBS support for XFS.

As I am preparing the next version of LBS patches for XFS, I could add this patch on top
and start running fstest for 8k block size on a system with 4k page size. I will let you
know if something blows up.

I haven't seen any new version of this series, so I will use this patch as a starting point
to test 8k filesystem blocksize.

-- 
Regards,
Pankaj


       reply	other threads:[~2024-01-22 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240122143620eucas1p1017072128a3b497fd95b796ebaad71a2@eucas1p1.samsung.com>
2024-01-22 14:36 ` Pankaj Raghav [this message]
2023-12-06 20:44 Matthew Wilcox (Oracle)
2023-12-06 20:53 ` Dave Chinner
2023-12-06 21:07 ` Yosry Ahmed
2024-02-05 12:00 ` Pankaj Raghav (Samsung)

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=6b93a509-fbaa-4311-8ee9-fd98e2fd2546@samsung.com \
    --to=p.raghav@samsung.com \
    --cc=20231206204442.771430-1-willy@infradead.org \
    --cc=djwong@kernel.org \
    --cc=hare@suse.com \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=slava@dubeyko.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