From: Matthew Wilcox <willy@infradead.org>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Creating large folios in iomap buffered write path
Date: Fri, 19 May 2023 16:38:28 +0100 [thread overview]
Message-ID: <ZGeX9Oc5vTkrceLZ@casper.infradead.org> (raw)
In-Reply-To: <20230519105528.1321.409509F4@e16-tech.com>
On Fri, May 19, 2023 at 10:55:29AM +0800, Wang Yugui wrote:
> Hi,
>
> > On Thu, May 18, 2023 at 10:46:43PM +0100, Matthew Wilcox wrote:
> > > -struct folio *iomap_get_folio(struct iomap_iter *iter, loff_t pos)
> > > +struct folio *iomap_get_folio(struct iomap_iter *iter, loff_t pos, size_t len)
> > > {
> > > unsigned fgp = FGP_WRITEBEGIN | FGP_NOFS;
> > > + struct folio *folio;
> > >
> > > if (iter->flags & IOMAP_NOWAIT)
> > > fgp |= FGP_NOWAIT;
> > > + fgp |= fgp_order(len);
> > >
> > > - return __filemap_get_folio(iter->inode->i_mapping, pos >> PAGE_SHIFT,
> > > + folio = __filemap_get_folio(iter->inode->i_mapping, pos >> PAGE_SHIFT,
> > > fgp, mapping_gfp_mask(iter->inode->i_mapping));
> > > + if (!IS_ERR(folio) && folio_test_large(folio))
> > > + printk("index:%lu len:%zu order:%u\n", (unsigned long)(pos / PAGE_SIZE), len, folio_order(folio));
> > > + return folio;
> > > }
> >
> > Forgot to take the debugging out. This should read:
> >
> > -struct folio *iomap_get_folio(struct iomap_iter *iter, loff_t pos)
> > +struct folio *iomap_get_folio(struct iomap_iter *iter, loff_t pos, size_t len)
> > {
> > unsigned fgp = FGP_WRITEBEGIN | FGP_NOFS;
> > if (iter->flags & IOMAP_NOWAIT)
> > fgp |= FGP_NOWAIT;
> > + fgp |= fgp_order(len);
> >
> > return __filemap_get_folio(iter->inode->i_mapping, pos >> PAGE_SHIFT,
> > fgp, mapping_gfp_mask(iter->inode->i_mapping));
> > }
>
> I test it (attachment file) on 6.4.0-rc2.
> fio -name write-bandwidth -rw=write -bs=1024Ki -size=32Gi -runtime=30 -iodepth 1 -ioengine sync -zero_buffers=1 -direct=0 -end_fsync=1 -numjobs=4 -directory=/mnt/test
>
> fio WRITE: bw=2430MiB/s.
> expected value: > 6000MiB/s
> so yet no fio write bandwidth improvement.
That's basically unchanged. There's no per-page or per-block work being
done in start/end writeback, so if Dave's investigation is applicable
to your situation, I'd expect to see an improvement.
Maybe try the second version of the patch I sent with the debug in,
to confirm you really are seeing large folios being created (you might
want to use printk_ratelimit() instead of printk to ensure it doesn't
overwhelm your system)? That fio command you were using ought to create
them, but there's always a chance it doesn't.
Perhaps you could use perf (the command Dave used) to see where the time
is being spent.
next prev parent reply other threads:[~2023-05-19 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230510165055.01D5.409509F4@e16-tech.com>
[not found] ` <20230511013410.GY3223426@dread.disaster.area>
[not found] ` <20230517210740.6464.409509F4@e16-tech.com>
2023-05-18 18:36 ` Creating large folios in iomap buffered write path Matthew Wilcox
2023-05-18 21:46 ` Matthew Wilcox
2023-05-18 22:03 ` Matthew Wilcox
2023-05-19 2:55 ` Wang Yugui
2023-05-19 15:38 ` Matthew Wilcox [this message]
2023-05-20 13:35 ` Wang Yugui
2023-05-20 16:35 ` Matthew Wilcox
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=ZGeX9Oc5vTkrceLZ@casper.infradead.org \
--to=willy@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
/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).