From: Michal Hocko <email@example.com> To: Alexander Duyck <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [mm PATCH v3 4/6] mm: Move hot-plug specific memory init into separate functions and optimize Date: Thu, 25 Oct 2018 14:41:15 +0200 [thread overview] Message-ID: <20181025124115.GQ18839@dhcp22.suse.cz> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed 24-10-18 10:35:09, Alexander Duyck wrote: > On Wed, 2018-10-24 at 17:27 +0200, Michal Hocko wrote: > > On Wed 24-10-18 08:08:41, Alexander Duyck wrote: > > > On Wed, 2018-10-24 at 14:36 +0200, Michal Hocko wrote: > > > > On Wed 17-10-18 08:26:20, Alexander Duyck wrote: > > > > [...] > > > > > With that said I am also wondering if a possible solution to > > > > > the complaints you had would be to look at just exporting the > > > > > __init_pageblock function later and moving the call to > > > > > memmap_init_zone_device out to the memremap or hotplug code > > > > > when Dan gets the refactoring for HMM and memremap all sorted > > > > > out. > > > > > > > > Why cannot we simply provide a constructor for each page by the > > > > caller if there are special requirements? we currently have > > > > alt_map > > > > to do struct page allocation but nothing really prevents to make > > > > it > > > > more generic and control both allocation and initialization > > > > whatever > > > > suits a specific usecase. I really do not want make special cases > > > > here and there. > > > > > > The advantage to the current __init_pageblock function is that we > > > end up constructing everything we are going to write outside of the > > > main loop and then are focused only on init. > > > > But we do really want move_pfn_range_to_zone to provide a usable pfn > > range without any additional tweaks. If there are potential > > optimizations to be done there then let's do it but please do not try > > to micro optimize to the point that the interface doesn't make any > > sense anymore. > > The actual difference between the two setups is not all that great. > >From the sound of things the ultimate difference between the > ZONE_DEVICE pages and regular pages is the pgmap and if we want the > reserved bit set or not. So once again, why do you need PageReserved in the first place. Alos it seems that pgmap can hold both the struct page allocator and constructor. > What I am providing with __init_pageblock at this point is a function > that is flexible enough for us to be able to do either one and then > just expose a different front end on it for the specific type of page > we have to initialize. It works for regular hotplug, ZONE_DEVICE, and > deferred memory initialization. The way I view it is that this funciton > is a high performance multi-tasker, not something that is micro- > optimized for any one specific function. All that I argue about is that all this should live inside the core hotplug. If you can plumb it there without hacks I have seen earlier then I do not mind but let's try to keep the core infrastructure as clelan as possible. -- Michal Hocko SUSE Labs
next prev parent reply other threads:[~2018-10-25 12:41 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-15 20:26 [mm PATCH v3 0/6] Deferred page init improvements Alexander Duyck 2018-10-15 20:26 ` [mm PATCH v3 1/6] mm: Use mm_zero_struct_page from SPARC on all 64b architectures Alexander Duyck 2018-10-16 19:01 ` Pavel Tatashin 2018-10-17 7:30 ` Mike Rapoport 2018-10-17 14:52 ` Alexander Duyck 2018-10-17 8:47 ` Michal Hocko 2018-10-17 15:07 ` Alexander Duyck 2018-10-17 15:12 ` Pavel Tatashin 2018-10-17 15:40 ` David Laight 2018-10-17 16:31 ` Alexander Duyck 2018-10-17 17:08 ` Pavel Tatashin 2018-10-17 16:34 ` Michal Hocko 2018-10-15 20:27 ` [mm PATCH v3 2/6] mm: Drop meminit_pfn_in_nid as it is redundant Alexander Duyck 2018-10-16 20:33 ` Pavel Tatashin 2018-10-16 20:49 ` Alexander Duyck 2018-10-16 21:06 ` Pavel Tatashin 2018-10-17 9:04 ` Michal Hocko 2018-10-15 20:27 ` [mm PATCH v3 3/6] mm: Use memblock/zone specific iterator for handling deferred page init Alexander Duyck 2018-10-17 9:11 ` Michal Hocko 2018-10-17 15:17 ` Alexander Duyck 2018-10-17 16:42 ` Mike Rapoport 2018-10-15 20:27 ` [mm PATCH v3 4/6] mm: Move hot-plug specific memory init into separate functions and optimize Alexander Duyck 2018-10-17 9:18 ` Michal Hocko 2018-10-17 15:26 ` Alexander Duyck 2018-10-24 12:36 ` Michal Hocko 2018-10-24 15:08 ` Alexander Duyck 2018-10-24 15:27 ` Michal Hocko 2018-10-24 17:35 ` Alexander Duyck 2018-10-25 12:41 ` Michal Hocko [this message] 2018-10-15 20:27 ` [mm PATCH v3 5/6] mm: Use common iterator for deferred_init_pages and deferred_free_pages Alexander Duyck 2018-10-15 20:27 ` [mm PATCH v3 6/6] mm: Add reserved flag setting to set_page_links Alexander Duyck
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=20181025124115.GQ18839@dhcp22.suse.cz \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [mm PATCH v3 4/6] mm: Move hot-plug specific memory init into separate functions and optimize' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).