From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759879AbcIWReE (ORCPT ); Fri, 23 Sep 2016 13:34:04 -0400 Received: from mga11.intel.com ([192.55.52.93]:30859 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759277AbcIWReC (ORCPT ); Fri, 23 Sep 2016 13:34:02 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,382,1470726000"; d="scan'208";a="12666373" Subject: Re: [PATCH] mm: warn about allocations which stall for too long To: Michal Hocko , linux-mm@kvack.org References: <20160923081555.14645-1-mhocko@kernel.org> Cc: Andrew Morton , Johannes Weiner , Mel Gorman , Tetsuo Handa , LKML , Michal Hocko From: Dave Hansen Message-ID: <57E56789.1070205@intel.com> Date: Fri, 23 Sep 2016 10:34:01 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <20160923081555.14645-1-mhocko@kernel.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/23/2016 01:15 AM, Michal Hocko wrote: > + /* Make sure we know about allocations which stall for too long */ > + if (!(gfp_mask & __GFP_NOWARN) && time_after(jiffies, alloc_start + stall_timeout)) { > + pr_warn("%s: page alloction stalls for %ums: order:%u mode:%#x(%pGg)\n", > + current->comm, jiffies_to_msecs(jiffies-alloc_start), > + order, gfp_mask, &gfp_mask); > + stall_timeout += 10 * HZ; > + dump_stack(); > + } This would make an awesome tracepoint. There's probably still plenty of value to having it in dmesg, but the configurability of tracepoints is hard to beat.