linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, linux-mm <linux-mm@kvack.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Shile Zhang <shile.zhang@linux.alibaba.com>,
	Daniel Jordan <daniel.m.jordan@oracle.com>,
	Kirill Tkhai <ktkhai@virtuozzo.com>,
	David Hildenbrand <david@redhat.com>,
	James Morris <jmorris@namei.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 2/2] mm: initialize deferred pages with interrupts enabled
Date: Thu, 2 Apr 2020 11:05:55 -0400	[thread overview]
Message-ID: <CA+CK2bDA4YOJWr8eKff3yowVS+TS+EdsjASes43ZLRiXs2jcsg@mail.gmail.com> (raw)
In-Reply-To: <8a2fbe6b-c861-9d47-9f02-72d476265359@suse.cz>

> TBH I don't remember my concern anymore. Reading my mail now [1] it seems I was
> thinking the problem could happen not just in interrupt context, but with other
> kthreads as well.
> Anyway I agree with the approach of waiting for actual issues being reported and
> then eventually pre-growing more.
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>

Thank you.

Pasha

      reply	other threads:[~2020-04-02 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 22:57 [PATCH v2 0/2] initialize deferred pages with interrupts enabled 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
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 [this message]

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=CA+CK2bDA4YOJWr8eKff3yowVS+TS+EdsjASes43ZLRiXs2jcsg@mail.gmail.com \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=daniel.m.jordan@oracle.com \
    --cc=david@redhat.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=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;
as well as URLs for NNTP newsgroup(s).