All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Ian Rickards <ian.rickards@arm.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Plans for F2FS Supporting Large Folios
Date: Mon, 7 Oct 2024 16:38:20 +0000	[thread overview]
Message-ID: <ZwQOfGaybpdC6_HW@google.com> (raw)
In-Reply-To: <671e8774-acaf-4c59-b06a-bf1511de022a@arm.com>

Hi Ryan,

On 10/02, Ryan Roberts wrote:
> Hi Jaegeuk Kim, Chao Yu,
> 
> I heard (via Matthew Wilcox) that you may be in the process of forming plans to
> add large folio support to f2fs? If so, I wonder if you could let me know how
> those plans are progressing? I saw your v6.12-rc1 pull request did a lot of
> conversion from struct page to struct folio (of the small variety for now) but
> wondered if this is intended as pre-work for enabling large folios?
> 
> I've been doing a lot of work on the anonymous memory side to support large
> folios ("mTHP") and hook that up to arm64's contpte pgtable support. This
> improves performance nicely.
> 
> Additionally I have experimented (on XFS) with ensuring that text mappings are
> contpte mapped where possible and this reduces pressure in the iTLB to improve
> performance further. But it all relies on the file system supporting large
> folios. I'd very much like to realize these performance gains on Android, but
> that requires the file systems that Android uses to support large folios.
> 
> It would be great to understand your plans, if any, and figure out if/where Arm
> may be able to help accelerate activities in this area. I'm not (yet!) an fs
> expert, but I see that f2fs is already using iomap, so perhaps now that you are
> supporting small folios, switching up to large folios is not too big of a step?

Thanks for sharing the background. By any chance, have you talked larg folio
with Android kernel team? If indeed there's a fair benefit from Android side,
I'd like to circle back supporting it in f2fs seriously.

> 
> Thanks,
> Ryan


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2024-10-07 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  8:32 [f2fs-dev] Plans for F2FS Supporting Large Folios Ryan Roberts
2024-10-07 16:38 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2024-10-09 11:23   ` Ryan Roberts
2024-10-29  9:19     ` Ryan Roberts

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=ZwQOfGaybpdC6_HW@google.com \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=ian.rickards@arm.com \
    --cc=jaegeuk@kernel.org \
    --cc=ryan.roberts@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.