From: Cody P Schafer <cody@linux.vnet.ibm.com> To: Andrew Morton <akpm@linux-foundation.org> Cc: Linux MM <linux-mm@kvack.org>, David Hansen <dave@linux.vnet.ibm.com>, LKML <linux-kernel@vger.kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Jiang Liu <liuj97@gmail.com>, Wen Congyang <wency@cn.fujitsu.com>, Lai Jiangshan <laijs@cn.fujitsu.com>, Wu Jianguo <wujianguo@huawei.com>, Tang Chen <tangchen@cn.fujitsu.com> Subject: Re: [PATCH v2 0/9] mm: zone & pgdat accessors plus some cleanup Date: Tue, 05 Feb 2013 14:59:23 -0800 [thread overview] Message-ID: <51118ECB.10006@linux.vnet.ibm.com> (raw) In-Reply-To: <20130201163924.75edfe40.akpm@linux-foundation.org> On 02/01/2013 04:39 PM, Andrew Morton wrote: > On Thu, 17 Jan 2013 14:52:52 -0800 > Cody P Schafer <cody@linux.vnet.ibm.com> wrote: > >> Summaries: >> 1 - avoid repeating checks for section in page flags by adding a define. >> 2 - add & switch to zone_end_pfn() and zone_spans_pfn() >> 3 - adds zone_is_initialized() & zone_is_empty() >> 4 - adds a VM_BUG using zone_is_initialized() in __free_one_page() >> 5 - add pgdat_end_pfn() and pgdat_is_empty() >> 6 - add debugging message to VM_BUG check. >> 7 - add ensure_zone_is_initialized() (for memory_hotplug) >> 8 - use the above addition in memory_hotplug >> 9 - use pgdat_end_pfn() > > Well that's a nice little patchset. > > Some of the patches were marked From:cody@linux.vnet.ibm.com and others > were From:jmesmon@gmail.com. This is strange. If you want me to fix > that up, please let me know which is preferred. They should all be "From:cody@linux.vnet.ibm.com", other address was me messing up gitconfig (which I've since fixed). >> As a general concern: spanned_pages & start_pfn (in pgdat & zone) are supposed >> to be locked (via a seqlock) when read (due to changes to them via >> memory_hotplug), but very few (only 1?) of their users appear to actually lock >> them. > > OK, thanks. Perhaps this is something which the memory-hotplug > developers could take a look at? Yep. It's not immediately clear that not locking on read would do terrible things, but at the least the documentation needs fixing and explanation as to why the locking is not used some (or all) places.
WARNING: multiple messages have this Message-ID (diff)
From: Cody P Schafer <cody@linux.vnet.ibm.com> To: Andrew Morton <akpm@linux-foundation.org> Cc: Linux MM <linux-mm@kvack.org>, David Hansen <dave@linux.vnet.ibm.com>, LKML <linux-kernel@vger.kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Jiang Liu <liuj97@gmail.com>, Wen Congyang <wency@cn.fujitsu.com>, Lai Jiangshan <laijs@cn.fujitsu.com>, Wu Jianguo <wujianguo@huawei.com>, Tang Chen <tangchen@cn.fujitsu.com> Subject: Re: [PATCH v2 0/9] mm: zone & pgdat accessors plus some cleanup Date: Tue, 05 Feb 2013 14:59:23 -0800 [thread overview] Message-ID: <51118ECB.10006@linux.vnet.ibm.com> (raw) In-Reply-To: <20130201163924.75edfe40.akpm@linux-foundation.org> On 02/01/2013 04:39 PM, Andrew Morton wrote: > On Thu, 17 Jan 2013 14:52:52 -0800 > Cody P Schafer <cody@linux.vnet.ibm.com> wrote: > >> Summaries: >> 1 - avoid repeating checks for section in page flags by adding a define. >> 2 - add & switch to zone_end_pfn() and zone_spans_pfn() >> 3 - adds zone_is_initialized() & zone_is_empty() >> 4 - adds a VM_BUG using zone_is_initialized() in __free_one_page() >> 5 - add pgdat_end_pfn() and pgdat_is_empty() >> 6 - add debugging message to VM_BUG check. >> 7 - add ensure_zone_is_initialized() (for memory_hotplug) >> 8 - use the above addition in memory_hotplug >> 9 - use pgdat_end_pfn() > > Well that's a nice little patchset. > > Some of the patches were marked From:cody@linux.vnet.ibm.com and others > were From:jmesmon@gmail.com. This is strange. If you want me to fix > that up, please let me know which is preferred. They should all be "From:cody@linux.vnet.ibm.com", other address was me messing up gitconfig (which I've since fixed). >> As a general concern: spanned_pages & start_pfn (in pgdat & zone) are supposed >> to be locked (via a seqlock) when read (due to changes to them via >> memory_hotplug), but very few (only 1?) of their users appear to actually lock >> them. > > OK, thanks. Perhaps this is something which the memory-hotplug > developers could take a look at? Yep. It's not immediately clear that not locking on read would do terrible things, but at the least the documentation needs fixing and explanation as to why the locking is not used some (or all) places. -- 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>
next prev parent reply other threads:[~2013-02-05 22:59 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-17 22:52 [PATCH v2 0/9] mm: zone & pgdat accessors plus some cleanup Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-01-17 22:52 ` [PATCH 1/9] mm: add SECTION_IN_PAGE_FLAGS Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-02-02 0:20 ` Andrew Morton 2013-02-02 0:20 ` Andrew Morton 2013-02-05 22:23 ` Cody P Schafer 2013-02-05 22:23 ` Cody P Schafer 2013-01-17 22:52 ` [PATCH 2/9] mm: add & use zone_end_pfn() and zone_spans_pfn() Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-01-17 22:52 ` [PATCH 3/9] mm: add zone_is_empty() and zone_is_initialized() Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-01-17 22:52 ` [PATCH 4/9] mm/page_alloc: add a VM_BUG in __free_one_page() if the zone is uninitialized Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-01-17 22:52 ` [PATCH 5/9] mmzone: add pgdat_{end_pfn,is_empty}() helpers & consolidate Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-02-02 0:23 ` Andrew Morton 2013-02-02 0:23 ` Andrew Morton 2013-01-17 22:52 ` [PATCH 6/9] mm/page_alloc: add informative debugging message in page_outside_zone_boundaries() Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-02-02 0:28 ` Andrew Morton 2013-02-02 0:28 ` Andrew Morton 2013-02-02 0:29 ` Andrew Morton 2013-02-02 0:29 ` Andrew Morton 2013-02-05 22:20 ` Cody P Schafer 2013-02-05 22:20 ` Cody P Schafer 2013-01-17 22:52 ` [PATCH 7/9] mm: add helper ensure_zone_is_initialized() Cody P Schafer 2013-01-17 22:52 ` Cody P Schafer 2013-01-17 22:53 ` [PATCH 8/9] mm/memory_hotplug: use ensure_zone_is_initialized() Cody P Schafer 2013-01-17 22:53 ` Cody P Schafer 2013-01-17 22:53 ` [PATCH 9/9] mm/memory_hotplug: use pgdat_end_pfn() instead of open coding the same Cody P Schafer 2013-01-17 22:53 ` Cody P Schafer 2013-02-02 0:39 ` [PATCH v2 0/9] mm: zone & pgdat accessors plus some cleanup Andrew Morton 2013-02-02 0:39 ` Andrew Morton 2013-02-05 22:59 ` Cody P Schafer [this message] 2013-02-05 22:59 ` Cody P Schafer
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=51118ECB.10006@linux.vnet.ibm.com \ --to=cody@linux.vnet.ibm.com \ --cc=akpm@linux-foundation.org \ --cc=catalin.marinas@arm.com \ --cc=dave@linux.vnet.ibm.com \ --cc=laijs@cn.fujitsu.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=liuj97@gmail.com \ --cc=tangchen@cn.fujitsu.com \ --cc=wency@cn.fujitsu.com \ --cc=wujianguo@huawei.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: 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.