From: Wang Yugui <wangyugui@e16-tech.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J . Wong" <djwong@kernel.org>
Subject: Re: [PATCH 0/3] Create large folios in iomap buffered write path
Date: Sun, 21 May 2023 19:40:54 +0800 [thread overview]
Message-ID: <20230521194053.8CD1.409509F4@e16-tech.com> (raw)
In-Reply-To: <20230520163603.1794256-1-willy@infradead.org>
Hi,
> Wang Yugui has a workload which would be improved by using large folios.
> Until now, we've only created large folios in the readahead path,
> but this workload writes without reading. The decision of what size
> folio to create is based purely on the size of the write() call (unlike
> readahead where we keep history and can choose to create larger folios
> based on that history even if individual reads are small).
>
> The third patch looks like it's an optional extra but is actually needed
> for the first two patches to work in the write path, otherwise it limits
> the length that iomap_get_folio() sees to PAGE_SIZE.
>
> Matthew Wilcox (Oracle) (3):
> filemap: Allow __filemap_get_folio to allocate large folios
> iomap: Create large folios in the buffered write path
> iomap: Copy larger chunks from userspace
The [PATCH 2/3] is a little difficult to backport to 6.1.y(LTS),
it need some patches as depency.
so please provide those patches based on 6.1.y(LTS) and depency list?
then we can do more test on 6.1.y(LTS) too.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/05/21
> fs/gfs2/bmap.c | 2 +-
> fs/iomap/buffered-io.c | 32 ++++++++++++++++++------------
> include/linux/iomap.h | 2 +-
> include/linux/pagemap.h | 29 ++++++++++++++++++++++++---
> mm/filemap.c | 44 ++++++++++++++++++++++++++++-------------
> mm/folio-compat.c | 2 +-
> mm/readahead.c | 13 ------------
> 7 files changed, 78 insertions(+), 46 deletions(-)
>
> --
> 2.39.2
next prev parent reply other threads:[~2023-05-21 11:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 16:36 [PATCH 0/3] Create large folios in iomap buffered write path Matthew Wilcox (Oracle)
2023-05-20 16:36 ` [PATCH 1/3] filemap: Allow __filemap_get_folio to allocate large folios Matthew Wilcox (Oracle)
2023-05-21 1:02 ` Wang Yugui
2023-05-21 1:56 ` Matthew Wilcox
2023-05-21 2:04 ` Wang Yugui
2023-05-21 3:39 ` Matthew Wilcox
2023-05-21 2:13 ` Dave Chinner
2023-05-21 3:38 ` Matthew Wilcox
2023-05-23 5:59 ` Christoph Hellwig
2023-05-23 12:17 ` Matthew Wilcox
2023-05-20 16:36 ` [PATCH 2/3] iomap: Create large folios in the buffered write path Matthew Wilcox (Oracle)
2023-05-20 16:36 ` [PATCH 3/3] iomap: Copy larger chunks from userspace Matthew Wilcox (Oracle)
2023-05-20 19:11 ` kernel test robot
2023-05-20 19:25 ` kernel test robot
2023-05-21 0:49 ` [PATCH 0/3] Create large folios in iomap buffered write path Wang Yugui
2023-05-21 0:59 ` Matthew Wilcox
2023-05-21 1:38 ` Wang Yugui
2023-05-21 2:49 ` Dave Chinner
2023-05-21 11:40 ` Wang Yugui [this message]
2023-05-31 4:34 ` Wang Yugui
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=20230521194053.8CD1.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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