mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v2 2/2] mm: initialize deferred pages with interrupts enabled
Date: Thu, 2 Apr 2020 09:14:42 +0200	[thread overview]
Message-ID: <875bcca7-7a95-d98f-ff0c-7eab224e6033@redhat.com> (raw)
In-Reply-To: <20200401225723.14164-3-pasha.tatashin@soleen.com>

On 02.04.20 00:57, Pavel Tatashin wrote:
> Initializing struct pages is a long task and keeping interrupts disabled
> for the duration of this operation introduces a number of problems.
> 
> 1. jiffies are not updated for long period of time, and thus incorrect time
>    is reported. See proposed solution and discussion here:
>    lkml/20200311123848.118638-1-shile.zhang@linux.alibaba.com
> 2. It prevents farther improving deferred page initialization by allowing
>    intra-node multi-threading.
> 
> We are keeping interrupts disabled to solve a rather theoretical problem
> that was never observed in real world (See 3a2d7fa8a3d5).
> 
> Lets keep interrupts enabled. In case we ever encounter a scenario where
> an interrupt thread wants to allocate large amount of memory this early in
> boot we can deal with that by growing zone (see deferred_grow_zone()) by
> the needed amount before starting deferred_init_memmap() threads.
> 
> Before:
> [    1.232459] node 0 initialised, 12058412 pages in 1ms
> 
> After:
> [    1.632580] node 0 initialised, 12051227 pages in 436ms
> 
> Fixes: 3a2d7fa8a3d5 ("mm: disable interrupts while initializing deferred pages")
> Cc: stable@vger.kernel.org # 4.17+
> 

Can you please add my details about the use of cond_resched() fixing
detection of RCU stalls?

https://lore.kernel.org/linux-mm/20200401104156.11564-2-david@redhat.com/

In the meantime, I'll give these two patches a churn. Thanks


-- 
Thanks,

David / dhildenb


  reply	other threads:[~2020-04-02  7:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 22:57 [PATCH v2 0/2] " Pavel Tatashin
2020-04-01 22:57 ` [PATCH v2 1/2] mm: call touch_nmi_watchdog() on max order boundaries in deferred init Pavel Tatashin
2020-04-02  7:23   ` David Hildenbrand
2020-04-02  7:46   ` Michal Hocko
2020-04-02 11:36   ` Vlastimil Babka
2020-04-01 22:57 ` [PATCH v2 2/2] mm: initialize deferred pages with interrupts enabled Pavel Tatashin
2020-04-02  7:14   ` David Hildenbrand [this message]
2020-04-02 15:49     ` Pavel Tatashin
2020-04-02  7:38   ` David Hildenbrand
2020-04-02  7:47     ` Michal Hocko
2020-04-02 15:13       ` Pavel Tatashin
2020-04-02 17:16         ` Michal Hocko
2020-04-02 18:25           ` Pavel Tatashin
2020-04-02 12:09   ` Vlastimil Babka
2020-04-02 15:05     ` Pavel Tatashin

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=875bcca7-7a95-d98f-ff0c-7eab224e6033@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®