From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Williams <dan.j.williams@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Johannes Thumshirn <jthumshirn@suse.de>,
Michal Hocko <mhocko@suse.com>
Subject: [PATCH 0/3] mm, memory_hotplug: fix few soft lockups in memory hotadd
Date: Mon, 18 Sep 2017 14:14:07 +0200 [thread overview]
Message-ID: <20170918121410.24466-1-mhocko@kernel.org> (raw)
Hi,
Johannes has noticed few soft lockups when adding a large nvdimm
device. All of them were caused by a long loop without any explicit
cond_resched which is a problem for !PREEMPT kernels. The fix is quite
straightforward. Just make sure that cond_resched gets called from time
to time.
Could you consider these for merging?
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Williams <dan.j.williams@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Johannes Thumshirn <jthumshirn@suse.de>,
Michal Hocko <mhocko@suse.com>
Subject: [PATCH 0/3] mm, memory_hotplug: fix few soft lockups in memory hotadd
Date: Mon, 18 Sep 2017 14:14:07 +0200 [thread overview]
Message-ID: <20170918121410.24466-1-mhocko@kernel.org> (raw)
Hi,
Johannes has noticed few soft lockups when adding a large nvdimm
device. All of them were caused by a long loop without any explicit
cond_resched which is a problem for !PREEMPT kernels. The fix is quite
straightforward. Just make sure that cond_resched gets called from time
to time.
Could you consider these for merging?
next reply other threads:[~2017-09-18 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 12:14 Michal Hocko [this message]
2017-09-18 12:14 ` [PATCH 0/3] mm, memory_hotplug: fix few soft lockups in memory hotadd Michal Hocko
2017-09-18 12:14 ` [PATCH 1/3] mm, memory_hotplug: add scheduling point to __add_pages Michal Hocko
2017-09-18 12:14 ` Michal Hocko
2017-09-18 12:16 ` Johannes Thumshirn
2017-09-18 12:16 ` Johannes Thumshirn
2017-09-18 12:14 ` [PATCH 2/3] mm, page_alloc: add scheduling point to memmap_init_zone Michal Hocko
2017-09-18 12:14 ` Michal Hocko
2017-09-18 12:17 ` Johannes Thumshirn
2017-09-18 12:17 ` Johannes Thumshirn
2017-09-18 12:14 ` [PATCH 3/3] memremap: add scheduling point to devm_memremap_pages Michal Hocko
2017-09-18 12:14 ` Michal Hocko
2017-09-18 12:17 ` Johannes Thumshirn
2017-09-18 12:17 ` Johannes Thumshirn
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=20170918121410.24466-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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.