From: zhong jiang <zhongjiang@huawei.com> To: Michal Hocko <mhocko@kernel.org> Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, lenb@kernel.org, akpm@linux-foundation.org, vbabka@suse.cz, linux-mm@kvack.org, richard.weiyang@gmail.com, pombredanne@nexb.com, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH] x86/numa: move setting parse numa node to num_add_memblk Date: Wed, 29 Nov 2017 21:26:19 +0800 [thread overview] Message-ID: <5A1EB57B.2080101@huawei.com> (raw) In-Reply-To: <20171129130158.hji24remijkaoydb@dhcp22.suse.cz> On 2017/11/29 21:01, Michal Hocko wrote: > On Wed 29-11-17 20:41:25, zhong jiang wrote: >> On 2017/11/29 20:03, Michal Hocko wrote: >>> On Wed 29-11-17 17:13:27, zhong jiang wrote: >>>> Currently, Arm64 and x86 use the common code wehn parsing numa node >>>> in a acpi way. The arm64 will set the parsed node in numa_add_memblk, >>>> but the x86 is not set in that , then it will result in the repeatly >>>> setting. And the parsed node maybe is unreasonable to the system. >>>> >>>> we would better not set it although it also still works. because the >>>> parsed node is unresonable. so we should skip related operate in this >>>> node. This patch just set node in various architecture individually. >>>> it is no functional change. >>> I really have hard time to understand what you try to say above. Could >>> you start by the problem description and then how you are addressing it? >> I am so sorry for that. I will make the issue clear. >> >> Arm64 get numa information through acpi. The code flow is as follows. >> >> arm64_acpi_numa_init >> acpi_parse_memory_affinity >> acpi_numa_memory_affinity_init >> numa_add_memblk(nid, start, end); //it will set node to numa_nodes_parsed successfully. >> node_set(node, numa_nodes_parsed); // numa_add_memblk had set that. it will repeat. >> >> the root cause is that X86 parse numa also go through above code. and arch-related >> numa_add_memblk is not set the parsed node to numa_nodes_parsed. it need >> additional node_set(node, numa_parsed) to handle. therefore, the issue will be introduced. >> > No it is not much more clear. I would have to go and re-study the whole > code flow to see what you mean here. So you could simply state what _the > issue_ is? How can user observe it and what are the consequences? The patch do not fix a real issue. it is a cleanup. because the acpi code is public, I find they are messy between Arch64 and X86 when parsing numa message . therefore, I try to make the code more clear between them. Thanks zhongjiang > Sorry for my laziness, I could go and read the code but the primary > point of the changelog is to be _clear_ about the problem and the fix. > Call paths can help reviewers but the scope should be clear even without > them. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com> To: Michal Hocko <mhocko@kernel.org> Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <x86@kernel.org>, <lenb@kernel.org>, <akpm@linux-foundation.org>, <vbabka@suse.cz>, <linux-mm@kvack.org>, <richard.weiyang@gmail.com>, <pombredanne@nexb.com>, <linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org> Subject: Re: [PATCH] x86/numa: move setting parse numa node to num_add_memblk Date: Wed, 29 Nov 2017 21:26:19 +0800 [thread overview] Message-ID: <5A1EB57B.2080101@huawei.com> (raw) In-Reply-To: <20171129130158.hji24remijkaoydb@dhcp22.suse.cz> On 2017/11/29 21:01, Michal Hocko wrote: > On Wed 29-11-17 20:41:25, zhong jiang wrote: >> On 2017/11/29 20:03, Michal Hocko wrote: >>> On Wed 29-11-17 17:13:27, zhong jiang wrote: >>>> Currently, Arm64 and x86 use the common code wehn parsing numa node >>>> in a acpi way. The arm64 will set the parsed node in numa_add_memblk, >>>> but the x86 is not set in that , then it will result in the repeatly >>>> setting. And the parsed node maybe is unreasonable to the system. >>>> >>>> we would better not set it although it also still works. because the >>>> parsed node is unresonable. so we should skip related operate in this >>>> node. This patch just set node in various architecture individually. >>>> it is no functional change. >>> I really have hard time to understand what you try to say above. Could >>> you start by the problem description and then how you are addressing it? >> I am so sorry for that. I will make the issue clear. >> >> Arm64 get numa information through acpi. The code flow is as follows. >> >> arm64_acpi_numa_init >> acpi_parse_memory_affinity >> acpi_numa_memory_affinity_init >> numa_add_memblk(nid, start, end); //it will set node to numa_nodes_parsed successfully. >> node_set(node, numa_nodes_parsed); // numa_add_memblk had set that. it will repeat. >> >> the root cause is that X86 parse numa also go through above code. and arch-related >> numa_add_memblk is not set the parsed node to numa_nodes_parsed. it need >> additional node_set(node, numa_parsed) to handle. therefore, the issue will be introduced. >> > No it is not much more clear. I would have to go and re-study the whole > code flow to see what you mean here. So you could simply state what _the > issue_ is? How can user observe it and what are the consequences? The patch do not fix a real issue. it is a cleanup. because the acpi code is public, I find they are messy between Arch64 and X86 when parsing numa message . therefore, I try to make the code more clear between them. Thanks zhongjiang > Sorry for my laziness, I could go and read the code but the primary > point of the changelog is to be _clear_ about the problem and the fix. > Call paths can help reviewers but the scope should be clear even without > them.
next prev parent reply other threads:[~2017-11-29 13:26 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-29 9:13 [PATCH] x86/numa: move setting parse numa node to num_add_memblk zhong jiang 2017-11-29 9:13 ` zhong jiang 2017-11-29 9:13 ` zhong jiang 2017-11-29 12:03 ` Michal Hocko 2017-11-29 12:03 ` Michal Hocko 2017-11-29 12:41 ` zhong jiang 2017-11-29 12:41 ` zhong jiang 2017-11-29 12:41 ` zhong jiang 2017-11-29 13:01 ` Michal Hocko 2017-11-29 13:01 ` Michal Hocko 2017-11-29 13:26 ` zhong jiang [this message] 2017-11-29 13:26 ` zhong jiang 2017-11-29 13:33 ` Michal Hocko 2017-11-29 13:33 ` Michal Hocko 2017-11-29 13:44 ` zhong jiang 2017-11-29 13:44 ` zhong jiang 2017-11-29 14:14 ` Dou Liyang 2017-11-29 14:14 ` Dou Liyang 2017-11-30 4:39 ` zhong jiang 2017-11-30 4:39 ` zhong jiang 2017-12-01 8:48 ` zhong jiang 2017-12-01 8:48 ` zhong jiang 2017-12-01 8:48 ` zhong jiang 2017-12-01 8:58 ` Michal Hocko 2017-12-01 8:58 ` Michal Hocko 2017-12-01 9:01 ` zhong jiang 2017-12-01 9:01 ` zhong jiang 2017-12-01 9:01 ` zhong jiang
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=5A1EB57B.2080101@huawei.com \ --to=zhongjiang@huawei.com \ --cc=akpm@linux-foundation.org \ --cc=lenb@kernel.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@kernel.org \ --cc=mingo@redhat.com \ --cc=pombredanne@nexb.com \ --cc=richard.weiyang@gmail.com \ --cc=tglx@linutronix.de \ --cc=vbabka@suse.cz \ --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: linkBe 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.