From: David Hildenbrand <david@redhat.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
Oscar Salvador <osalvador@suse.de>,
linux-mm@kvack.org, akpm@linux-foundation.org,
anshuman.khandual@arm.com
Subject: Re: [PATCH v2] mm/sparse: set section nid for hot-add memory
Date: Wed, 19 Jun 2019 11:11:12 +0200 [thread overview]
Message-ID: <40817af2-992e-adb6-3053-fc8f570050a4@redhat.com> (raw)
In-Reply-To: <20190619090824.GK2968@dhcp22.suse.cz>
On 19.06.19 11:08, Michal Hocko wrote:
> On Wed 19-06-19 11:03:49, David Hildenbrand wrote:
>> On 19.06.19 11:01, Michal Hocko wrote:
> [...]
>>> And if they do need a smaller granularity to describe their
>>> memory topology then we need a different user API rather the fiddle with
>>> implementation details I would argue.
>>>
>>
>> It is not about supporting it, it is about properly blocking it.
>
> We already do that in test_pages_in_a_zone, right? Albeit in
> MAX_ORDER_NR_PAGES granularity.
>
Indeed, thanks for pointing that out. I knew that we were checking zones
but had in my head that it was working on zone idx.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-06-19 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 0:55 Wei Yang
2019-06-18 7:49 ` Oscar Salvador
2019-06-18 8:32 ` Wei Yang
2019-06-18 8:40 ` David Hildenbrand
2019-06-19 6:10 ` Michal Hocko
2019-06-19 8:54 ` David Hildenbrand
2019-06-19 9:01 ` Michal Hocko
2019-06-19 9:03 ` David Hildenbrand
2019-06-19 9:08 ` Michal Hocko
2019-06-19 9:11 ` David Hildenbrand [this message]
2019-06-19 6:23 ` Michal Hocko
2019-06-19 7:53 ` Oscar Salvador
2019-06-19 8:51 ` David Hildenbrand
2019-06-19 9:04 ` Michal Hocko
2019-06-19 9:07 ` David Hildenbrand
2019-06-19 9:16 ` Michal Hocko
2019-06-19 9:30 ` David Hildenbrand
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=40817af2-992e-adb6-3053-fc8f570050a4@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=richardw.yang@linux.intel.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