> -----Original Message----- > From: Michal Hocko [mailto:mho...@suse.cz] > Sent: Monday, July 22, 2013 8:37 AM > To: KY Srinivasan > Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com; > a...@firstfloor.org; a...@linux-foundation.org; linux...@kvack.org; > kamezawa.hiroy...@gmail.com; han...@cmpxchg.org; ying...@google.com; > jasow...@redhat.com; k...@vrfy.org > Subject: Re: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining > memory blocks > > On Fri 19-07-13 12:23:05, K. Y. Srinivasan wrote: > > The current machinery for hot-adding memory requires having udev > > rules to bring the memory segments online. Export the necessary > > functionality > > to to bring the memory segment online without involving user space code. > > Why? Who is going to use it and for what purpose? > If you need to do it from the kernel cannot you use usermod helper > thread? > > Besides that this is far from being complete. memory_block_change_state > seems to depend on device_hotplug_lock and find_memory_block is > currently called with mem_sysfs_mutex held. None of them is exported > AFAICS.
You are right; not all of the required symbols are exported (yet). Let me answer your other questions first: The Hyper-V balloon driver can use this functionality. I have prototyped the in-kernel "onlining" of hot added memory without requiring any help from user level code that performs significantly better than having user level code involved in the hot add process. With this change, I am able to successfully hot-add and online the hot-added memory even under extreme memory pressure which is what you would want given that we are hot-adding memory to alleviate memory pressure. The current scheme of involving user level code to close this loop obviously does not perform well under high memory pressure. I can, if you prefer export all of the necessary functionality in one patch. Regards, K. Y -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
