From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Cc: djwong@kernel.org, hch@lst.de, kent.overstreet@linux.dev,
willy@infradead.org,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Dave Chinner <david@fromorbit.com>
Subject: [ANNOUNCE] xfs-linux: iomap-for-next updated to d42bd17c6a20
Date: Mon, 24 Jul 2023 17:45:28 -0700 [thread overview]
Message-ID: <20230725004528.GB11336@frogsfrogsfrogs> (raw)
Hi folks,
The iomap-for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update.
So. I've merged willy's large folio writes series into the branch, and
next I'd like to merge Ritesh's dirty block tracking changes. Ritesh,
could you rebase your changes against this branch and send me a pull
request?
(Next in line could be the dio completions thing that Jens is working
on, though iirc Dave still had some questions about that...)
The new head of the iomap-for-next branch is commit:
d42bd17c6a20 Merge tag 'large-folio-writes' of git://git.infradead.org/users/willy/pagecache into iomap-6.6-merge
11 new commits:
Darrick J. Wong (1):
[d42bd17c6a20] Merge tag 'large-folio-writes' of git://git.infradead.org/users/willy/pagecache into iomap-6.6-merge
Matthew Wilcox (Oracle) (10):
[f7f9a0c8736d] iov_iter: Map the page later in copy_page_from_iter_atomic()
[908a1ad89466] iov_iter: Handle compound highmem pages in copy_page_from_iter_atomic()
[1b0306981e0f] iov_iter: Add copy_folio_from_iter_atomic()
[a221ab717c43] iomap: Remove large folio handling in iomap_invalidate_folio()
[32b29cc9db45] doc: Correct the description of ->release_folio
[7a8eb01b078f] iomap: Remove unnecessary test from iomap_release_folio()
[ffc143db63ee] filemap: Add fgf_t typedef
[4f6617011910] filemap: Allow __filemap_get_folio to allocate large folios
[d6bb59a9444d] iomap: Create large folios in the buffered write path
[5d8edfb900d5] iomap: Copy larger chunks from userspace
Code Diffstat:
Documentation/filesystems/locking.rst | 15 +++++--
fs/btrfs/file.c | 6 +--
fs/f2fs/compress.c | 2 +-
fs/f2fs/f2fs.h | 2 +-
fs/gfs2/bmap.c | 2 +-
fs/iomap/buffered-io.c | 54 +++++++++++------------
include/linux/iomap.h | 2 +-
include/linux/pagemap.h | 82 ++++++++++++++++++++++++++++++-----
include/linux/uio.h | 9 +++-
lib/iov_iter.c | 43 +++++++++++-------
mm/filemap.c | 65 ++++++++++++++-------------
mm/folio-compat.c | 2 +-
mm/readahead.c | 13 ------
13 files changed, 187 insertions(+), 110 deletions(-)
reply other threads:[~2023-07-25 0:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230725004528.GB11336@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ritesh.list@gmail.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;
as well as URLs for NNTP newsgroup(s).