From: KY Srinivasan <kys@microsoft.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kamezawa.hiroyuki@gmail.com" <kamezawa.hiroyuki@gmail.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"yinghan@google.com" <yinghan@google.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"kay@vrfy.org" <kay@vrfy.org>
Subject: RE: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks
Date: Tue, 23 Jul 2013 14:52:36 +0000 [thread overview]
Message-ID: <e06fced3ca42408b980f8aa68f4a29f3@SN2PR03MB061.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20130722123716.GB24400@dhcp22.suse.cz>
> -----Original Message-----
> From: Michal Hocko [mailto:mhocko@suse.cz]
> Sent: Monday, July 22, 2013 8:37 AM
> To: KY Srinivasan
> Cc: gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com;
> andi@firstfloor.org; akpm@linux-foundation.org; linux-mm@kvack.org;
> kamezawa.hiroyuki@gmail.com; hannes@cmpxchg.org; yinghan@google.com;
> jasowang@redhat.com; kay@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, 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-07-23 14:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 19:23 K. Y. Srinivasan
2013-07-22 3:16 ` Jason Wang
2013-07-22 12:37 ` Michal Hocko
2013-07-23 14:52 ` KY Srinivasan [this message]
2013-07-23 15:09 ` Michal Hocko
2013-07-23 15:50 ` KY Srinivasan
2013-07-23 15:28 ` Dave Hansen
2013-07-23 15:54 ` KY Srinivasan
2013-07-23 16:00 ` Dave Hansen
2013-07-23 17:21 ` KY Srinivasan
2013-07-24 16:43 ` Dave Hansen
2013-07-24 19:45 ` KY Srinivasan
2013-07-24 21:02 ` Dave Hansen
2013-07-25 7:57 ` Michal Hocko
2013-07-25 11:14 ` KY Srinivasan
2013-07-25 15:03 ` Dave Hansen
2013-07-25 15:15 ` Kay Sievers
2013-07-25 16:35 ` Dave Hansen
2013-07-25 15:49 ` KY Srinivasan
2013-07-23 16:01 ` Greg KH
2013-07-23 16:54 ` KY Srinivasan
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=e06fced3ca42408b980f8aa68f4a29f3@SN2PR03MB061.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=jasowang@redhat.com \
--cc=kamezawa.hiroyuki@gmail.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=olaf@aepfle.de \
--cc=yinghan@google.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox