* Dave Hansen <dave.hansen@xxxxxxxxx> [2016-08-03 12:40:17]: > On 08/02/2016 11:35 PM, Srikar Dronamraju wrote: > > On a regular kernel with CONFIG_FADUMP and fadump configured, 5% of the > > total memory is reserved for booting the kernel on crash. On crash, > > fadump kernel reserves the 95% memory and boots into the 5% memory that > > was reserved for it. It then parses the reserved 95% memory to collect > > the dump. > > > > The problem is not about the amount of memory thats reserved for fadump > > kernel. Even if we increase/decrease, we will still end up with the same > > issue. > > Oh, and the dentry/inode caches are sized based on 100% of memory, not > the 5% that's left after the fadump reservation? Yes, the dentry/inode caches are sized based on the 100% memory. > > Is the deferred initialization kicked in progress at the time we do the > dentry/inode allocations? Can waiting a bit let the allocation succeed? > Right now deferred initialisation kicks in after dentry/inode allocations. Can we defer the cache allocations till deferred initialisation? I dont know. But if we can that could potentially solve the problem. May be Mel or somebody might be able answer if we can defer dentry/inode cache allocations till deferred initialisation kicks in. The other idea is to detect nodes whose memory is reserved and allocate extra memory from the nodes where memory is not yet reserved. -- Thanks and Regards Srikar Dronamraju -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>