From: "Bodeddula, Balasubramaniam" <bodeddub@amazon.com>
To: "songmuchun@bytedance.com" <songmuchun@bytedance.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"almasrymina@google.com" <almasrymina@google.com>,
"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
"bp@alien8.de" <bp@alien8.de>, "corbet@lwn.net" <corbet@lwn.net>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"david@redhat.com" <david@redhat.com>,
"duanxiongchun@bytedance.com" <duanxiongchun@bytedance.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"jroedel@suse.de" <jroedel@suse.de>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"luto@kernel.org" <luto@kernel.org>,
"mchehab+huawei@kernel.org" <mchehab+huawei@kernel.org>,
"mhocko@suse.com" <mhocko@suse.com>,
"mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
"oneukum@suse.com" <oneukum@suse.com>,
"osalvador@suse.de" <osalvador@suse.de>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"pawan.kumar.gupta@linux.intel.com"
<pawan.kumar.gupta@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"rientjes@google.com" <rientjes@google.com>,
"song.bao.hua@hisilicon.com" <song.bao.hua@hisilicon.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"willy@infradead.org" <willy@infradead.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v17 1/9] mm: memory_hotplug: factor out bootmem core functions to bootmem_info.c
Date: Fri, 26 Feb 2021 18:06:18 +0000 [thread overview]
Message-ID: <FE7425D7-3006-4F31-AE41-07E4EB6D030F@contoso.com> (raw)
In-Reply-To: <<20210225132130.26451-2-songmuchun@bytedance.com>>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Tested-by: bodeddub@amazon.com
We are interested in this patch and have tested an earlier version of this patch on 5.11-rc4 kernel version. I did a functional validation of the changes and saw that the total memory listed by free command increasing and more memory was made available when memory was allocated in hugepages. 1G hugepages gave higher improvements compared to 2M, as expected. Is there a formal way to publish the results? I can do the same as required (I am new to Linux Kernel patching process).
I have a few follow-up questions on this patch:
1. What is the overall status of this patch? What is the ballpark timeline we are looking for this patch to be accepted.
2. Why is this patch not working when memory is allocated as hugepages by THP (transparent hugepages). THP uses AnonHugePages, doesn’t this patch generalize for all ‘type’ of hugepages?
Please let me know if there are any additional tasks that I can help. Happy to help.
Thanks.
[-- Attachment #2: Type: text/html, Size: 4041 bytes --]
next parent reply other threads:[~2021-02-26 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20210225132130.26451-2-songmuchun@bytedance.com>
2021-02-26 18:06 ` Bodeddula, Balasubramaniam [this message]
2021-03-01 3:01 ` [External] Re: [PATCH v17 1/9] mm: memory_hotplug: factor out bootmem core functions to bootmem_info.c Muchun Song
2021-03-01 3:01 ` Muchun Song
2021-02-25 13:21 [PATCH v17 0/9] Free some vmemmap pages of HugeTLB page Muchun Song
2021-02-25 13:21 ` [PATCH v17 1/9] mm: memory_hotplug: factor out bootmem core functions to bootmem_info.c Muchun Song
2021-03-03 2:45 ` Singh, Balbir
2021-03-04 4:26 ` Balbir Singh
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=FE7425D7-3006-4F31-AE41-07E4EB6D030F@contoso.com \
--to=bodeddub@amazon.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=anshuman.khandual@arm.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=duanxiongchun@bytedance.com \
--cc=hpa@zytor.com \
--cc=joao.m.martins@oracle.com \
--cc=jroedel@suse.de \
--cc=linmiaohe@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=naoya.horiguchi@nec.com \
--cc=oneukum@suse.com \
--cc=osalvador@suse.de \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=song.bao.hua@hisilicon.com \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.