From: Oscar Salvador <osalvador@suse.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <OSalvador@suse.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: do not report isolation failures for CMA pages
Date: Tue, 18 Dec 2018 13:21:07 +0100 [thread overview]
Message-ID: <20181218122107.vyvkxa5xg4hhfhtb@d104.suse.de> (raw)
In-Reply-To: <20181218112822.GG30879@dhcp22.suse.cz>
On Tue, Dec 18, 2018 at 12:28:22PM +0100, Michal Hocko wrote:
> Well, I haven't seen any reports about hugetlb pages so I didn't bother
> to mention it. Is this really important to note?
I guess not.
>
> > "Only report isolation failures from memhotplug code" ?
>
> only report isolation failures when offlining memory
Yes, that looks good.
--
Oscar Salvador
SUSE L3
prev parent reply other threads:[~2018-12-18 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 9:28 Michal Hocko
2018-12-18 10:18 ` Oscar Salvador
2018-12-18 11:28 ` Michal Hocko
2018-12-18 12:21 ` Oscar Salvador [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=20181218122107.vyvkxa5xg4hhfhtb@d104.suse.de \
--to=osalvador@suse.de \
--cc=OSalvador@suse.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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