linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] filemap: Convert generic_perform_write() to support large folios
Date: Tue, 22 Aug 2023 22:56:12 +0100	[thread overview]
Message-ID: <ZOUu/AGuQ8f+SWxU@casper.infradead.org> (raw)
In-Reply-To: <20230822211720.GA11242@frogsfrogsfrogs>

On Tue, Aug 22, 2023 at 02:17:20PM -0700, Darrick J. Wong wrote:
> On Tue, Aug 22, 2023 at 09:09:37PM +0100, Matthew Wilcox (Oracle) wrote:
> > Modelled after the loop in iomap_write_iter(), copy larger chunks from
> > userspace if the filesystem has created large folios.
> 
> Hum.  Which filesystems are those?  Is this for the in-memory ones like
> tmpfs?

Alas tmpfs uses its own shmem_file_read_iter() and doesn't call back
into generic_perform_write().  But I was looking at the ramfs aops and
thinking those looked ripe for large folio support, so I thought I'd take
care of this part first since it potentially affects every filesystem
that uses generic_file_write_iter() / __generic_file_write_iter() /
generic_perform_write().

This is also a great opporunity for someone to tell me "Actually I have
plans in this area and ..."


      reply	other threads:[~2023-08-22 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 20:09 [RFC PATCH] filemap: Convert generic_perform_write() to support large folios Matthew Wilcox (Oracle)
2023-08-22 21:17 ` Darrick J. Wong
2023-08-22 21:56   ` Matthew Wilcox [this message]

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=ZOUu/AGuQ8f+SWxU@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.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).