From: Oscar Salvador <osalvador@suse.de>
To: Muchun Song <songmuchun@bytedance.com>
Cc: David Hildenbrand <david@redhat.com>,
corbet@lwn.net, akpm@linux-foundation.org, paulmck@kernel.org,
mike.kravetz@oracle.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
duanxiongchun@bytedance.com, smuchun@gmail.com
Subject: Re: [PATCH v2 2/2] mm: memory_hotplug: introduce SECTION_CANNOT_OPTIMIZE_VMEMMAP
Date: Fri, 17 Jun 2022 11:48:36 +0200 [thread overview]
Message-ID: <YqxN9FMDnbo1+PnL@localhost.localdomain> (raw)
In-Reply-To: <YqwtCu2Ura+skV3B@FVFYT0MHHV2J.usts.net>
On Fri, Jun 17, 2022 at 03:28:10PM +0800, Muchun Song wrote:
> I think here needs a loop if it is a 1GB page (spans multiple sections).
> Right? Here is an implementation based on another approach. But I think
> your implementation is more simpler and efficient. Would you mind me
> squash your diff into my patch and with your "Co-developed-by"?
Sure, fine by me.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2022-06-17 9:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 2:55 [PATCH v2 0/2] make hugetlb_optimize_vmemmap compatible with memmap_on_memory Muchun Song
2022-05-20 2:55 ` [PATCH v2 1/2] mm: memory_hotplug: enumerate all supported section flags Muchun Song
2022-06-15 9:35 ` David Hildenbrand
2022-06-15 13:02 ` Muchun Song
2022-05-20 2:55 ` [PATCH v2 2/2] mm: memory_hotplug: introduce SECTION_CANNOT_OPTIMIZE_VMEMMAP Muchun Song
2022-06-15 9:51 ` David Hildenbrand
2022-06-16 2:45 ` Muchun Song
2022-06-16 7:21 ` David Hildenbrand
2022-06-16 10:16 ` Muchun Song
2022-06-16 3:57 ` Oscar Salvador
2022-06-16 7:30 ` David Hildenbrand
2022-06-17 5:46 ` Oscar Salvador
2022-06-17 7:28 ` Muchun Song
2022-06-17 7:39 ` David Hildenbrand
2022-06-17 9:10 ` Muchun Song
2022-06-17 9:25 ` David Hildenbrand
2022-06-17 9:40 ` Muchun Song
2022-06-17 9:48 ` Oscar Salvador [this message]
2022-06-17 7:43 ` David Hildenbrand
2022-06-17 9:54 ` Oscar Salvador
2022-06-17 10:14 ` David Hildenbrand
2022-06-17 10:49 ` Muchun Song
2022-06-17 11:19 ` Muchun Song
2022-06-18 5:49 ` Muchun Song
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=YqxN9FMDnbo1+PnL@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=duanxiongchun@bytedance.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=paulmck@kernel.org \
--cc=smuchun@gmail.com \
--cc=songmuchun@bytedance.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