From: Zaslonko Mikhail <zaslonko@linux.bm.com>
To: Michal Hocko <mhocko@kernel.org>,
Zaslonko Mikhail <zaslonko@linux.ibm.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"gerald.schaefer@de.ibm.com" <gerald.schaefer@de.ibm.com>,
schwidefsky@de.ibm.com
Subject: Re: Memory hotplug vmem pages
Date: Wed, 31 Oct 2018 16:52:57 +0100 [thread overview]
Message-ID: <8c13868c-8fa2-01e8-9940-767be087256f@linux.bm.com> (raw)
In-Reply-To: <20181030134433.GE32673@dhcp22.suse.cz>
Hello Michal,
Thanks for your response and for the link. I'm gonna play around with that patchset.
Thanks,
Mikhail Zaslonko
On 30.10.2018 14:44, Michal Hocko wrote:
> [Sorry for late response]
>
> On Fri 12-10-18 10:15:26, Zaslonko Mikhail wrote:
>> Hello Michal,
>>
>> I've read a recent discussion about introducing the memory types for memory
>> hotplug:
>> https://marc.info/?t=153814716600004&r=1&w=2
>>
>> In particular I was interested in the idea of moving vmem struct pages to
>> the hotplugable memory itself. I'm also looking into it for s390 right now.
>> So, in one of your replies you mentioned that you "have proposed (but
>> haven't finished this due to other stuff) a solution for this". Have you
>> covered any part of that solution yet? Could you please point me to any
>> relevant discussions on this matter?
>
> the patchset has been posted here [1]. I didn't get around to fix the
> hotremove case when you have to be extra carefule to not remove pfn
> range that backs struct pages still in use. I didn't have problems for
> small systems but 2GB memblocks just crashed.
>
> [1] http://lkml.kernel.org/r/20170801124111.28881-1-mhocko@kernel.org
>
prev parent reply other threads:[~2018-10-31 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 8:15 Zaslonko Mikhail
2018-10-30 13:44 ` Michal Hocko
2018-10-31 15:52 ` Zaslonko Mikhail [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=8c13868c-8fa2-01e8-9940-767be087256f@linux.bm.com \
--to=zaslonko@linux.bm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=zaslonko@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox