From: Christoph Hellwig <hch@lst.de>
To: David Howells <dhowells@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
netfs@lists.linux.dev, v9fs@lists.linux.dev,
linux-afs@lists.infradead.org, ceph-devel@vger.kernel.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
devel@lists.orangefs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm: Replace ->launder_folio() with flush and wait
Date: Thu, 7 Mar 2024 15:54:45 +0100 [thread overview]
Message-ID: <20240307145445.GA28823@lst.de> (raw)
In-Reply-To: <1831809.1709807788@warthog.procyon.org.uk>
On Thu, Mar 07, 2024 at 10:36:28AM +0000, David Howells wrote:
> There are some places that should perhaps be using kiocb_invalidate_pages()
> and kiocb_invalidate_post_direct_write() instead - assuming Christoph has no
> objection to the latter function being exported.
These are intended as helpers for direct I/O implementation, so I
very much expected them to eventually get exported.
next prev parent reply other threads:[~2024-03-07 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 22:39 [RFC PATCH] mm: Replace ->launder_folio() with flush and wait David Howells
2024-03-07 4:45 ` Matthew Wilcox
2024-03-07 8:26 ` David Howells
2024-03-07 10:36 ` David Howells
2024-03-07 14:54 ` Christoph Hellwig [this message]
2024-03-08 7:52 ` Miklos Szeredi
2024-03-19 14:14 ` David Howells
2024-03-19 16:13 ` Miklos Szeredi
2024-03-19 16:40 ` Miklos Szeredi
2024-03-19 16:59 ` Bernd Schubert
2024-03-07 16:15 ` [RFC PATCH v2] mm: Kill ->launder_folio() David Howells
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=20240307145445.GA28823@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=devel@lists.orangefs.org \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=netfs@lists.linux.dev \
--cc=trond.myklebust@hammerspace.com \
--cc=v9fs@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).