[lkml]   [2015]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high
Hi Baoquan,

thanks for your reply.

On Fri, Jan 23, 2015 at 04:44:53PM +0800, Baoquan He wrote:
> 2) increase low-mem when crashkernel=high. But we have to be careful to
> do this. We implement crashkernel=high not only for the unhappiness
> crashkernel reservation is limited below 4G, but dma/dma32 memory space
> is precious on some systems. If set crashkernel=high still too much low
> memory has to be reserved by default, it's important to find the
> balance. So if we have to increase the default low-mem, how much memory
> is enough, why 256M? why not 128M/192M/320M/384M? And if 256M works
> on your system, what if another person say it does't work because there
> are more devices on his system?
> Anyway, I understand the requirement, but we need find out how much
> memory can satisfy most of systems.

Yes, I totally agree that it is tough to find a good default here. I
used 256MB because this is what was required on the system the failed
kdumps were reported on.

But probably we can agree that 72MB is not enough (given that 64MB are
taken away by swiotlb already), and increase it to a value we think by
now is sufficient for most systems.

Btw, the issue was also reported on machines with only a few devices,
the reason there is that device drivers allocate more dma memory by
default on intilization. Maybe we should handle that as a driver
regression in the future, forcing them to allocate more dma-memory
on-demand and not on initialization.


 \ /
  Last update: 2015-01-26 13:21    [W:0.065 / U:8.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site