From: Chris Mason <clm@fb.com>
To: Dave Chinner <david@fromorbit.com>
Cc: djwong@kernel.org, hch@infradead.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, hannes@cmpxchg.org
Subject: Re: [PATCH v2] iomap: skip pages past eof in iomap_do_writepage()
Date: Sat, 11 Jun 2022 19:34:01 -0400 [thread overview]
Message-ID: <fb72ebb9-df11-7689-0113-5d98783039fd@fb.com> (raw)
In-Reply-To: <8f4177bd-80ad-5e22-293e-5d1e944e1921@fb.com>
On 6/9/22 5:15 PM, Chris Mason wrote:
> On 6/8/22 8:53 PM, Dave Chinner wrote:
>> Reviewed-by: Dave Chinner <dchinner@redhat.com>
>
> Thanks! Johannes and I are both going on vacation, but I'll get an
> experiment rolled to enough hosts to see if the long tails get shorter.
> We're unlikely to come back with results before July.
>
Of course, the easiest way to test my theory is live patching against
v5.6, but there's a wrinkle because v5.6 still has xfs_vm_writepage()
Looks like the iomap conversion deleted the warning that Jan was
originally fixing, and I went through some hoops to trigger skipping the
pages from inside writepage(). As you noted in the commit to delete
writepage, this is pretty hard to trigger but it does happen once I get
down to a few hundred MB free. It doesn't seem to impact fsx runs or
other load, and we unmount/xfs_repair cleanly.
I don't like to ask people to think about ancient kernels, but am I
missing any huge problems? I've got this patch backported on v5.6, and
writepage is still in place.
-chris
next prev parent reply other threads:[~2022-06-11 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 0:42 [PATCH v2] iomap: skip pages past eof in iomap_do_writepage() Chris Mason
2022-06-08 18:27 ` Matthew Wilcox
2022-06-09 0:53 ` Dave Chinner
2022-06-09 21:15 ` Chris Mason
2022-06-11 23:34 ` Chris Mason [this message]
2022-06-13 22:04 ` Dave Chinner
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=fb72ebb9-df11-7689-0113-5d98783039fd@fb.com \
--to=clm@fb.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--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