Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753385AbbHaOqJ (ORCPT ); Mon, 31 Aug 2015 10:46:09 -0400 Received: from mail-yk0-f175.google.com ([209.85.160.175]:33867 "EHLO mail-yk0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753223AbbHaOqH (ORCPT ); Mon, 31 Aug 2015 10:46:07 -0400 Date: Mon, 31 Aug 2015 10:46:04 -0400 From: Tejun Heo To: Vladimir Davydov Cc: Michal Hocko , Andrew Morton , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] Fix memcg/memory.high in case kmem accounting is enabled Message-ID: <20150831144604.GD2271@mtj.duckdns.org> References: <20150831132414.GG29723@dhcp22.suse.cz> <20150831142049.GV9610@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150831142049.GV9610@esperanza> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 942 Lines: 26 Hello, Vladimir. On Mon, Aug 31, 2015 at 05:20:49PM +0300, Vladimir Davydov wrote: ... > That being said, this is the fix at the right layer. While this *might* be a necessary workaround for the hard limit case right now, this is by no means the fix at the right layer. The expectation is that mm keeps a reasonable amount of memory available for allocations which can't block. These allocations may fail from time to time depending on luck and under extreme memory pressure but the caller should be able to depend on it as a speculative allocation mechanism which doesn't fail willy-nilly. Hardlimit breaking GFP_NOWAIT behavior is a bug on memcg side, not slab or slub. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/