From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by kanga.kvack.org (Postfix) with ESMTP id 3056F6B0035 for ; Mon, 20 Jan 2014 05:37:41 -0500 (EST) Received: by mail-pb0-f45.google.com with SMTP id un15so3157212pbc.18 for ; Mon, 20 Jan 2014 02:37:40 -0800 (PST) Received: from szxga03-in.huawei.com (szxga03-in.huawei.com. [119.145.14.66]) by mx.google.com with ESMTPS id ot3si925436pac.137.2014.01.20.02.37.35 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 20 Jan 2014 02:37:39 -0800 (PST) Message-ID: <52DCFC33.80008@huawei.com> Date: Mon, 20 Jan 2014 18:36:35 +0800 From: Jianguo Wu MIME-Version: 1.0 Subject: [question] how to figure out OOM reason? should dump slab/vmalloc info when OOM? Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton , Johannes Weiner , Rik van Riel , David Rientjes , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" When OOM happen, will dump buddy free areas info, hugetlb pages info, memory state of all eligible tasks, per-cpu memory info. But do not dump slab/vmalloc info, sometime, it's not enough to figure out the reason OOM happened. So, my questions are: 1. Should dump slab/vmalloc info when OOM happen? Though we can get these from proc file, but usually we do not monitor the logs and check proc file immediately when OOM happened. 2. /proc/$pid/smaps and pagecache info also helpful when OOM, should also be dumped? 3. Without these info, usually how to figure out OOM reason? -- 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: email@kvack.org