From: Dave Chinner <david@fromorbit.com>
To: Jeffrey Baker <jwbaker@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Recurring hand in XFS inode reclaim on 4.10
Date: Thu, 30 May 2019 08:20:04 +1000 [thread overview]
Message-ID: <20190529222004.GD29573@dread.disaster.area> (raw)
In-Reply-To: <CAMCX63wUkBh==QFoeRSTxFKGdoo5iDLS6hM5xcVLK8_LfVdhwg@mail.gmail.com>
On Tue, May 28, 2019 at 10:16:39AM -0700, Jeffrey Baker wrote:
> On Sun, May 26, 2019 at 8:32 PM Dave Chinner <david@fromorbit.com> wrote:
> > On Fri, May 24, 2019 at 01:34:58PM -0700, Jeffrey Baker wrote:
> > > Write rates on the nvme drives are all exactly the md0 rates / 4, so
> > > that seems normal.
> >
> > Write rates aren't that important - what do the io latencies, queue
> > depths and device utilisation figures look like?
>
> 10s of microseconds, ~zero, and ~zero respectively.
So it sounds like the devices aren't showing signs of slowness, but
the filesystem and memory reclaim is sitting there twiddling it's
thumbs waiting for IO to complete?
Perhaps it might be worthwhile running a latency trace (e.g. with
ftrace or one of the newfangled bpf tools) to find out where
everything is blocking and how long they are waiting for things to
occur. That might give some more insight into what resource we are
waiting to be released to make progress...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2019-05-29 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 16:21 Recurring hand in XFS inode reclaim on 4.10 Jeffrey Baker
2019-05-21 22:49 ` Dave Chinner
2019-05-24 20:34 ` Jeffrey Baker
2019-05-27 3:32 ` Dave Chinner
2019-05-28 17:16 ` Jeffrey Baker
2019-05-29 22:20 ` Dave Chinner [this message]
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=20190529222004.GD29573@dread.disaster.area \
--to=david@fromorbit.com \
--cc=jwbaker@gmail.com \
--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