linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Sleeping BUG in khugepaged for i586
Date: Mon, 12 Jun 2017 08:29:18 +0200	[thread overview]
Message-ID: <20170612062918.GA4145@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1706111621330.36347@chino.kir.corp.google.com>

On Sun 11-06-17 16:28:11, David Rientjes wrote:
> On Sat, 10 Jun 2017, Michal Hocko wrote:
> 
> > > > I would just pull the cond_resched out of __collapse_huge_page_copy
> > > > right after pte_unmap. But I am not really sure why this cond_resched is
> > > > really needed because the changelog of the patch which adds is is quite
> > > > terse on details.
> > > 
> > > I'm not sure what could possibly be added to the changelog.  We have 
> > > encountered need_resched warnings during the iteration.
> > 
> > Well, the part the changelog is not really clear about is whether the
> > HPAGE_PMD_NR loops itself is the source of the stall. This would be
> > quite surprising because doing 512 iterations taking up to 20+s sounds
> > way to much.
> 
> I have no idea where you come up with 20+ seconds.

OK, I misread your report as a soft lockup.

> These are not soft lockups, these are need_resched warnings.  We monitor 
> how long need_resched has been set and when a thread takes an excessive 
> amount of time to reschedule after it has been set.  A loop of 512 pages 
> with ptl contention and doing {clear,copy}_user_highpage() shows that 
> need_resched can sit without scheduling for an excessive amount of time.

How much is excessive here?
-- 
Michal Hocko
SUSE Labs

--
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>

  reply	other threads:[~2017-06-12  6:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 19:24 Sleeping BUG in khugepaged for i586 Larry Finger
2017-06-05 21:44 ` Andrew Morton
2017-06-06 14:02   ` Vlastimil Babka
2017-06-06 15:01     ` Larry Finger
2017-06-07  7:19       ` Vlastimil Babka
2017-06-07 20:56         ` David Rientjes
2017-06-08 14:48           ` Michal Hocko
2017-06-08 17:05             ` Matthew Wilcox
2017-06-08 20:18               ` Michal Hocko
2017-06-08 20:30                 ` Michal Hocko
2017-06-09  6:48                   ` Vlastimil Babka
2017-06-09  7:43                     ` Michal Hocko
2017-06-09 14:28                     ` Larry Finger
2017-06-09 22:38                   ` David Rientjes
2017-06-10  8:09                     ` Michal Hocko
2017-06-11 23:28                       ` David Rientjes
2017-06-12  6:29                         ` Michal Hocko [this message]
2017-06-15  0:28                           ` David Rientjes
2017-06-15  1:12             ` David Rientjes
2017-06-15  8:32               ` Michal Hocko
2017-06-23 12:08             ` Michal Hocko
2017-06-23 13:13               ` Vlastimil Babka
2017-06-23 13:25                 ` Michal Hocko
2017-06-23 15:28                   ` Larry Finger
2017-06-08 15:29           ` Larry Finger

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=20170612062918.GA4145@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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).