From: Matthew Wilcox <willy@infradead.org>
To: Chi Zhiling <chizhiling@163.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chi Zhiling <chizhiling@kylinos.cn>
Subject: Re: [PATCH v2 3/5] mm/shmem: introduce copy_zero_to_iter() for large zeroing
Date: Mon, 1 Jun 2026 14:22:04 +0100 [thread overview]
Message-ID: <ah2HfH3jJZDiNAQc@casper.infradead.org> (raw)
In-Reply-To: <20260601055704.167436-4-chizhiling@163.com>
On Mon, Jun 01, 2026 at 01:57:02PM +0800, Chi Zhiling wrote:
> Currently, holes larger than PAGE_SIZE cannot be handled because
> ZERO_PAGE is limited to a single page. Add copy_zero_to_iter() as a
> wrapper to support copying larger zero ranges to the iterator.
I think Hugh put this optimisation in the wrong place, and you're
perpetuating that ;-)
So perhaps we can start by moving this optimisation to lib/iov_iter.c?
And then you can redo your optimisation on top of that.
diff --git a/lib/iov_iter.c b/lib/iov_iter.c
index 243662af1af7..06c54d719fcd 100644
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
@@ -451,7 +451,23 @@ static __always_inline
size_t zero_to_user_iter(void __user *iter_to, size_t progress,
size_t len, void *priv, void *priv2)
{
- return clear_user(iter_to, len);
+ /*
+ * it is noticeably faster to copy the zero page instead of
+ * calling clear_user(). Shame.
+ */
+ void *from = page_address(ZERO_PAGE(0));
+ size_t res = 0;
+
+ while (1) {
+ size_t n = min(len, PAGE_SIZE);
+ n = copy_to_user_iter(iter_to, progress, n, from, priv2);
+ res += n;
+ len -= n;
+ if (!len || !n)
+ break;
+ }
+
+ return res;
}
static __always_inline
diff --git a/mm/shmem.c b/mm/shmem.c
index 3b5dc21b323c..112cae9f9e4f 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3427,19 +3427,7 @@ static ssize_t shmem_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
else
ret = copy_page_to_iter(page, offset, nr, to);
folio_put(folio);
- } else if (user_backed_iter(to)) {
- /*
- * Copy to user tends to be so well optimized, but
- * clear_user() not so much, that it is noticeably
- * faster to copy the zero page instead of clearing.
- */
- ret = copy_page_to_iter(ZERO_PAGE(0), offset, nr, to);
} else {
- /*
- * But submitting the same page twice in a row to
- * splice() - or others? - can result in confusion:
- * so don't attempt that optimization on pipes etc.
- */
ret = iov_iter_zero(nr, to);
}
next prev parent reply other threads:[~2026-06-01 13:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 5:56 [PATCH v2 0/5] mm/shmem: optimize read with reduced xarray lookups and folio batching Chi Zhiling
2026-06-01 5:57 ` [PATCH v2 1/5] mm/filemap: reduce unnecessary xarray lookups when read cached pages Chi Zhiling
2026-06-01 12:51 ` Matthew Wilcox
2026-06-01 14:39 ` Chi Zhiling
2026-06-01 5:57 ` [PATCH v2 2/5] mm/filemap: reduce xarray lookups in filemap_get_folios_contig() Chi Zhiling
2026-06-01 5:57 ` [PATCH v2 3/5] mm/shmem: introduce copy_zero_to_iter() for large zeroing Chi Zhiling
2026-06-01 13:22 ` Matthew Wilcox [this message]
2026-06-01 14:57 ` Chi Zhiling
2026-06-01 15:02 ` Mateusz Guzik
2026-06-01 15:11 ` Mateusz Guzik
2026-06-01 15:13 ` Matthew Wilcox
2026-06-01 15:40 ` Mateusz Guzik
2026-06-01 22:03 ` David Laight
2026-06-01 5:57 ` [PATCH v2 4/5] mm/shmem: remove page-copy fallback in shmem read path Chi Zhiling
2026-06-02 5:39 ` Baolin Wang
2026-06-02 6:17 ` Chi Zhiling
2026-06-01 5:57 ` [PATCH v2 5/5] mm/shmem: optimize file read with folio batching Chi Zhiling
2026-06-01 13:59 ` Matthew Wilcox
2026-06-01 15:00 ` Chi Zhiling
2026-06-02 5:54 ` Baolin Wang
2026-06-02 6:58 ` Chi Zhiling
2026-06-01 7:16 ` [PATCH v2 0/5] mm/shmem: optimize read with reduced xarray lookups and " Chi Zhiling
2026-06-02 0:43 ` Andrew Morton
2026-06-02 2:44 ` Chi Zhiling
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=ah2HfH3jJZDiNAQc@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chizhiling@163.com \
--cc=chizhiling@kylinos.cn \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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