From: Dave Chinner <david@fromorbit.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: freezing system for several second on high I/O [kernel 4.15]
Date: Mon, 19 Feb 2018 16:02:09 +1100 [thread overview]
Message-ID: <20180219050209.GY7000@dastard> (raw)
In-Reply-To: <CABXGCsMK61J_+3c4JaXoi1e6aZzngvkQ29zRvQAj3nNcRpv5-Q@mail.gmail.com>
On Sun, Feb 18, 2018 at 07:02:37PM +0500, Mikhail Gavrilov wrote:
> On 16 February 2018 at 02:48, Dave Chinner <david@fromorbit.com> wrote:
> > On Fri, Feb 16, 2018 at 12:02:28AM +0500, Mikhail Gavrilov wrote:
> >> On 15 February 2018 at 10:44, Dave Chinner <david@fromorbit.com> wrote:
> >> > I've already explained that we can't annotate these memory
> >> > allocations to turn off the false positives because that will also
> >> > turning off all detection of real deadlock conditions. Lockdep has
> >> > many, many limitations, and this happens to be one of them.
> >> >
> >> > FWIW, is there any specific reason you running lockdep on your
> >> > desktop system?
> >>
> >> Because I wanna make open source better (help fixing all freezing)
> >
> > lockdep isn't a user tool - most developers don't even understand
> > what it tries to tell them. Worse, it is likely contributing to your
> > problems as it has a significant runtime CPU and memory overhead....
>
> I don't know how else collect debug info about freezes which occurring
> accidentally. Is there a better idea?
Lockdep tells us about locking problems, not arbitrary operational
latencies. Go look at the bcc collection of tools for tracking down
where latencies occur in the system.
-Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: freezing system for several second on high I/O [kernel 4.15]
Date: Mon, 19 Feb 2018 16:02:09 +1100 [thread overview]
Message-ID: <20180219050209.GY7000@dastard> (raw)
In-Reply-To: <CABXGCsMK61J_+3c4JaXoi1e6aZzngvkQ29zRvQAj3nNcRpv5-Q@mail.gmail.com>
On Sun, Feb 18, 2018 at 07:02:37PM +0500, Mikhail Gavrilov wrote:
> On 16 February 2018 at 02:48, Dave Chinner <david@fromorbit.com> wrote:
> > On Fri, Feb 16, 2018 at 12:02:28AM +0500, Mikhail Gavrilov wrote:
> >> On 15 February 2018 at 10:44, Dave Chinner <david@fromorbit.com> wrote:
> >> > I've already explained that we can't annotate these memory
> >> > allocations to turn off the false positives because that will also
> >> > turning off all detection of real deadlock conditions. Lockdep has
> >> > many, many limitations, and this happens to be one of them.
> >> >
> >> > FWIW, is there any specific reason you running lockdep on your
> >> > desktop system?
> >>
> >> Because I wanna make open source better (help fixing all freezing)
> >
> > lockdep isn't a user tool - most developers don't even understand
> > what it tries to tell them. Worse, it is likely contributing to your
> > problems as it has a significant runtime CPU and memory overhead....
>
> I don't know how else collect debug info about freezes which occurring
> accidentally. Is there a better idea?
Lockdep tells us about locking problems, not arbitrary operational
latencies. Go look at the bcc collection of tools for tracking down
where latencies occur in the system.
-Dave.
--
Dave Chinner
david@fromorbit.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-19 5:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:40 freezing system for several second on high I/O [kernel 4.15] mikhail
2018-01-31 2:22 ` Dave Chinner
2018-01-31 2:22 ` Dave Chinner
2018-02-05 3:25 ` mikhail
2018-02-06 3:47 ` mikhail
2018-02-06 6:08 ` Dave Chinner
2018-02-06 6:08 ` Dave Chinner
2018-02-06 7:12 ` Mikhail Gavrilov
2018-02-06 7:12 ` Mikhail Gavrilov
2018-02-07 3:40 ` mikhail
2018-02-07 6:55 ` Dave Chinner
2018-02-07 6:55 ` Dave Chinner
2018-02-10 9:34 ` mikhail
2018-02-10 9:34 ` mikhail
2018-02-10 9:35 ` mikhail
2018-02-11 22:56 ` Dave Chinner
2018-02-11 22:56 ` Dave Chinner
2018-02-14 21:27 ` mikhail
2018-02-14 21:27 ` mikhail
2018-02-14 21:52 ` Dave Chinner
2018-02-14 21:52 ` Dave Chinner
2018-02-15 3:40 ` mikhail
2018-02-15 3:42 ` mikhail
2018-02-15 3:42 ` mikhail
2018-02-15 3:46 ` Matthew Wilcox
2018-02-15 3:46 ` Matthew Wilcox
2018-02-15 5:44 ` Dave Chinner
2018-02-15 5:44 ` Dave Chinner
2018-02-15 19:02 ` Mikhail Gavrilov
2018-02-15 19:02 ` Mikhail Gavrilov
2018-02-15 21:48 ` Dave Chinner
2018-02-15 21:48 ` Dave Chinner
2018-02-18 14:02 ` Mikhail Gavrilov
2018-02-18 14:02 ` Mikhail Gavrilov
2018-02-19 5:02 ` Dave Chinner [this message]
2018-02-19 5:02 ` 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=20180219050209.GY7000@dastard \
--to=david@fromorbit.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mikhail.v.gavrilov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.