From: David Hildenbrand <david@redhat.com>
To: Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mhocko@suse.com, linux-mm@kvack.org, dan.j.williams@intel.com,
shile.zhang@linux.alibaba.com, daniel.m.jordan@oracle.com,
ktkhai@virtuozzo.com, jmorris@namei.org, sashal@kernel.org,
vbabka@suse.cz
Subject: Re: [PATCH v4 3/3] mm: call cond_resched() from deferred_init_memmap()
Date: Fri, 3 Apr 2020 17:17:54 +0200 [thread overview]
Message-ID: <4fb5a025-c5d9-abb5-b063-16a22c8443f6@redhat.com> (raw)
In-Reply-To: <20200403140952.17177-4-pasha.tatashin@soleen.com>
On 03.04.20 16:09, Pavel Tatashin wrote:
> Now that deferred pages are initialized with interrupts enabled we can
> replace touch_nmi_watchdog() with cond_resched(), as it was before
> 3a2d7fa8a3d5.
>
> For now, we cannot do the same in deferred_grow_zone() as it is still
> initializes pages with interrupts disabled.
>
> This change fixes RCU problem described:
> linux-mm/20200401104156.11564-2-david@redhat.com
BTW,
https://lkml.kernel.org/r/20200401104156.11564-2-david@redhat.com
Would be better.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-04-03 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 14:09 [PATCH v4 0/3] initialize deferred pages with interrupts enabled Pavel Tatashin
2020-04-03 14:09 ` [PATCH v4 1/3] mm: call touch_nmi_watchdog() on max order boundaries in deferred init Pavel Tatashin
2020-04-03 14:09 ` [PATCH v4 2/3] mm: initialize deferred pages with interrupts enabled Pavel Tatashin
2020-04-03 15:18 ` David Hildenbrand
2020-04-03 14:09 ` [PATCH v4 3/3] mm: call cond_resched() from deferred_init_memmap() Pavel Tatashin
2020-04-03 14:12 ` Michal Hocko
2020-04-03 15:16 ` David Hildenbrand
2020-04-03 15:17 ` David Hildenbrand [this message]
2020-04-06 7:02 ` Pankaj Gupta
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=4fb5a025-c5d9-abb5-b063-16a22c8443f6@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=daniel.m.jordan@oracle.com \
--cc=jmorris@namei.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@soleen.com \
--cc=sashal@kernel.org \
--cc=shile.zhang@linux.alibaba.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®