Messages in this thread | | | From | KY Srinivasan <> | Subject | RE: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks | Date | Tue, 23 Jul 2013 15:54:10 +0000 |
| |
> -----Original Message----- > From: Dave Hansen [mailto:dave.hansen@intel.com] > Sent: Tuesday, July 23, 2013 11:28 AM > To: KY Srinivasan > Cc: Michal Hocko; 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 07/23/2013 07:52 AM, KY Srinivasan wrote: > > The current scheme of involving user > > level code to close this loop obviously does not perform well under high > memory pressure. > > Adding memory usually requires allocating some large, contiguous areas > of memory for use as mem_map[] and other VM structures. That's really > hard to do under heavy memory pressure. How are you accomplishing this?
I cannot avoid failures because of lack of memory. In this case I notify the host of the failure and also tag the failure as transient. Host retries the operation after some delay. There is no guarantee it will succeed though.
K. Y > > >
| |