linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richard.weiyang@linux.alibaba.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Oscar Salvador <osalvador@suse.de>, Linux MM <linux-mm@kvack.org>,
	Baoquan He <bhe@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/spase: never partially remove memmap for early section
Date: Tue, 30 Jun 2020 09:16:09 +0200	[thread overview]
Message-ID: <e98997ed-4a9f-37cc-932b-9ac9c4441291@redhat.com> (raw)
In-Reply-To: <20200629225842.GA38617@L-31X9LVDL-1304.local>

On 30.06.20 00:58, Wei Yang wrote:
> On Mon, Jun 29, 2020 at 03:13:25PM -0700, Dan Williams wrote:
>> On Mon, Jun 29, 2020 at 1:34 AM Wei Yang
>> <richard.weiyang@linux.alibaba.com> wrote:
>>>
>>> On Thu, Jun 25, 2020 at 12:46:43PM -0700, Dan Williams wrote:
>>>> On Wed, Jun 24, 2020 at 10:53 PM David Hildenbrand <david@redhat.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Am 25.06.2020 um 01:47 schrieb Dan Williams <dan.j.williams@intel.com>:
>>>>>>
>>>>>> On Wed, Jun 24, 2020 at 3:44 PM Wei Yang
>>>>>> <richard.weiyang@linux.alibaba.com> wrote:
>>>>>> [..]
>>>>>>>> So, you are right that there is a mismatch here, but I think the
>>>>>>>> comprehensive fix is to allow early sections to be partially
>>>>>>>> depopulated/repopulated rather than have section_activate() and
>>>>>>>> section_deacticate() special case early sections. The special casing
>>>>>>>> is problematic in retrospect as section_deactivate() can't be
>>>>>>>> maintained without understand special rules in section_activate().
>>>>>>>
>>>>>>> Hmm... This means we need to adjust pfn_valid() too, which always return true
>>>>>>> for early sections.
>>>>>>
>>>>>> Right, rather than carry workarounds in 3 locations, and the bug that
>>>>>> has resulted from then getting out of sync, just teach early section
>>>>>> mapping to allow for the subsection populate/depopulate.
>>>>>>
>>>>>
>>>>> I prefer the easy fix first - IOW what we Here here. Especially, pfn_to_online_page() will need changes as well.
>>>>
>>>> Agree, yes, let's do the simple fix first for 5.8 and the special-case
>>>> elimination work later.
>>>
>>> Dan,
>>>
>>> A quick test shows this is not a simple task.
>>
>> Thanks for taking a look...
>>
>>> First, early sections don't set subsection bitmap, which is necessary for the
>>> hot-add/remove.
>>>
>>> To properly set subsection bitmap, we need to know how many subsections in
>>> early section. While current code doesn't has a alignment requirement for
>>> last early section. We mark the whole last early section as present.
>>
>> I was thinking that the subsection map does not need to be accurate on
>> initial setup, it only needs to be accurate after the first removal.
>> However, that would result in new special casing that somewhat defeats
>> the purpose. The hardest part is potentially breaking up a PMD mapping
>> of the page array into a series of PTE mappings without disturbing
>> in-flight pfn_to_page() users.
>>
>>> I don't find a way to enable this.
>>
>> While I don't like that this bug crept into the mismatched special
>> casing of early sections, I'm now coming around to the same opinion.
>> I.e. that making the memmap for early sections permanent is a simpler
>> mechanism to maintain.
> 
> I think so ...
> 

Yes, and I think having to replace quite some pfn_valid_within() - nops
- by pfn_valid() just to handle one corner case might not be worth it.
At least for now.

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2020-06-30  7:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  9:42 Wei Yang
2020-06-23 12:44 ` David Hildenbrand
2020-06-23 13:02   ` Wei Yang
2020-06-23 13:16     ` David Hildenbrand
2020-06-23 15:18 ` Michal Hocko
2020-06-23 21:48   ` Wei Yang
2020-06-24  6:13   ` Wei Yang
2020-06-24 16:10     ` Dan Williams
2020-06-24 22:05       ` Wei Yang
2020-06-24 22:20         ` Dan Williams
2020-06-24 22:44           ` Wei Yang
2020-06-24 23:47             ` Dan Williams
2020-06-25  5:53               ` David Hildenbrand
2020-06-25 19:46                 ` Dan Williams
2020-06-25 22:29                   ` Wei Yang
2020-06-29  8:34                   ` Wei Yang
2020-06-29 22:13                     ` Dan Williams
2020-06-29 22:58                       ` Wei Yang
2020-06-30  7:16                         ` David Hildenbrand [this message]
2020-06-25 22:39                 ` Wei Yang
2020-06-26  4:59                   ` David Hildenbrand
2020-06-24  7:48   ` David Hildenbrand
2020-06-24  8:04     ` David Hildenbrand
2020-06-24  8:13     ` Wei Yang
2020-06-24  8:41       ` David Hildenbrand
2020-06-24  8:50         ` Michal Hocko
2020-06-24 22:27         ` Wei Yang
2020-06-24  0:21 ` Dan Williams
2020-06-24  1:11   ` Wei Yang
2020-06-24  1:47   ` Baoquan He
2020-06-24  2:14     ` Baoquan He
2020-06-24  3:46     ` Wei Yang
2020-06-24  3:52       ` Baoquan He
2020-06-24  3:56         ` Wei Yang
2020-06-24  8:51           ` David Hildenbrand
2020-06-24 22:08             ` Wei Yang

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=e98997ed-4a9f-37cc-932b-9ac9c4441291@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=osalvador@suse.de \
    --cc=richard.weiyang@linux.alibaba.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