linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Michael Stapelberg <michael+lkml@stapelberg.ch>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Jack Smith <smith.jack.sidman@gmail.com>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [fuse-devel] Writing to FUSE via mmap extremely slow (sometimes) on some machines?
Date: Tue, 3 Mar 2020 09:13:11 -0500	[thread overview]
Message-ID: <20200303141311.GA189690@mtj.thefacebook.com> (raw)
In-Reply-To: <CANnVG6=i1VmWF0aN1tJo5+NxTv6ycVOQJnpFiqbD7ZRVR6T4=Q@mail.gmail.com>

Hello,

On Tue, Mar 03, 2020 at 03:03:58PM +0100, Michael Stapelberg wrote:
> Here’s a /proc/<pid>/stack from when the issue is happening:
> 
> [<0>] balance_dirty_pages_ratelimited+0x2ca/0x3b0
> [<0>] __handle_mm_fault+0xe6e/0x1280
> [<0>] handle_mm_fault+0xbe/0x1d0
> [<0>] __do_page_fault+0x249/0x4f0
> [<0>] page_fault+0x1e/0x30
> 
> How can I obtain the numbers for the next step?

Yes, that's dirty throttling alright. Hopefully, the
balance_dirty_pages tracepoint which can be enabled from under
/sys/kernel/debug/tracing/events/writeback/balance_dirty_pages/ should
tell us why bdp thinks it needs throttling and then we can go from
there. Unfortunately, I'm rather preoccupied and afraid I don't have a
lot of bandwidth to work on it myself for the coming weeks.

Thanks.

-- 
tejun


  reply	other threads:[~2020-03-03 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANnVG6kZzN1Ja0EmxG3pVTdMx8Kf8fezGWBtCYUzk888VaFThg@mail.gmail.com>
     [not found] ` <CACQJH27s4HKzPgUkVT+FXWLGqJAAMYEkeKe7cidcesaYdE2Vog@mail.gmail.com>
     [not found]   ` <CANnVG6=Ghu5r44mTkr0uXx_ZrrWo2N5C_UEfM59110Zx+HApzw@mail.gmail.com>
     [not found]     ` <CAJfpegvzhfO7hg1sb_ttQF=dmBeg80WVkV8srF3VVYHw9ybV0w@mail.gmail.com>
     [not found]       ` <CANnVG6kSJJw-+jtjh-ate7CC3CsB2=ugnQpA9ACGFdMex8sftg@mail.gmail.com>
2020-02-26 19:59         ` [fuse-devel] Writing to FUSE via mmap extremely slow (sometimes) on some machines? Miklos Szeredi
2020-03-03 10:34           ` Michael Stapelberg
2020-03-03 13:04           ` Tejun Heo
2020-03-03 14:03             ` Michael Stapelberg
2020-03-03 14:13               ` Tejun Heo [this message]
2020-03-03 14:21                 ` Michael Stapelberg
2020-03-03 14:25                   ` Tejun Heo
2020-03-05 14:45                     ` Michael Stapelberg
2020-03-09 14:32                       ` Michael Stapelberg
2020-03-09 14:36                         ` Miklos Szeredi
2020-03-09 15:11                           ` Michael Stapelberg
2020-03-12 15:45                             ` Michael Stapelberg

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=20200303141311.GA189690@mtj.thefacebook.com \
    --to=tj@kernel.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=michael+lkml@stapelberg.ch \
    --cc=miklos@szeredi.hu \
    --cc=smith.jack.sidman@gmail.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).