From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC v3 3/3] iomap: bound ioend size to 4096 pages
Date: Wed, 19 May 2021 14:28:39 +0100 [thread overview]
Message-ID: <YKUSh4DVMCTzlSOE@infradead.org> (raw)
In-Reply-To: <20210517171722.1266878-4-bfoster@redhat.com>
On Mon, May 17, 2021 at 01:17:22PM -0400, Brian Foster wrote:
> The iomap writeback infrastructure is currently able to construct
> extremely large bio chains (tens of GBs) associated with a single
> ioend. This consolidation provides no significant value as bio
> chains increase beyond a reasonable minimum size. On the other hand,
> this does hold significant numbers of pages in the writeback
> state across an unnecessarily large number of bios because the ioend
> is not processed for completion until the final bio in the chain
> completes. Cap an individual ioend to a reasonable size of 4096
> pages (16MB with 4k pages) to avoid this condition.
Note that once we get huge page/folio support in the page cache this
sucks as we can trivially handle much larger sizes with very little
iteration.
I wonder if both this limit and the previous one should be based on the
number of pages added instead. And in fact maybe if we only want the
limit at add to ioend time and skip the defer to workqueue part entirely.
next prev parent reply other threads:[~2021-05-19 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 17:17 [PATCH v3 0/3] iomap: avoid soft lockup warnings on large ioends Brian Foster
2021-05-17 17:17 ` [PATCH v3 1/3] iomap: resched ioend completion when in non-atomic context Brian Foster
2021-05-17 17:54 ` Matthew Wilcox
2021-05-18 11:38 ` Brian Foster
2021-05-20 21:58 ` Darrick J. Wong
2021-05-24 11:57 ` Brian Foster
2021-05-24 16:53 ` Darrick J. Wong
2021-05-26 1:19 ` Darrick J. Wong
2021-05-22 7:45 ` Ming Lei
2021-05-24 11:57 ` Brian Foster
2021-05-24 14:11 ` Ming Lei
2021-05-17 17:17 ` [PATCH v3 2/3] xfs: kick large ioends to completion workqueue Brian Foster
2021-05-26 1:20 ` Darrick J. Wong
2021-05-17 17:17 ` [PATCH RFC v3 3/3] iomap: bound ioend size to 4096 pages Brian Foster
2021-05-19 13:28 ` Christoph Hellwig [this message]
2021-05-19 14:52 ` Brian Foster
2021-05-20 23:27 ` Darrick J. Wong
2021-05-24 12:02 ` Brian Foster
2021-05-25 4:20 ` Darrick J. Wong
2021-05-25 4:29 ` Damien Le Moal
2021-05-25 7:13 ` Dave Chinner
2021-05-25 9:07 ` Andreas Gruenbacher
2021-05-26 2:12 ` Matthew Wilcox
2021-05-26 3:32 ` Darrick J. Wong
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=YKUSh4DVMCTzlSOE@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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).