From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f199.google.com (mail-wr0-f199.google.com [209.85.128.199]) by kanga.kvack.org (Postfix) with ESMTP id 3A7596B0033 for ; Mon, 27 Nov 2017 14:47:57 -0500 (EST) Received: by mail-wr0-f199.google.com with SMTP id u98so14145068wrb.17 for ; Mon, 27 Nov 2017 11:47:57 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id i30sor8074519wra.60.2017.11.27.11.47.56 for (Google Transport Security); Mon, 27 Nov 2017 11:47:56 -0800 (PST) Date: Mon, 27 Nov 2017 22:47:53 +0300 From: Alexey Dobriyan Subject: Re: [PATCH] mm: disable `vm.max_map_count' sysctl limit Message-ID: <20171127194753.GB28115@avx2> References: <20171127194603.GA28115@avx2> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171127194603.GA28115@avx2> Sender: owner-linux-mm@kvack.org List-ID: To: mikpelinux@gmail.com Cc: linux-kernel@vger.kernel.org, mhocko@kernel.org, willy@infradead.org, ak@linux.intel.com, linux-mm@kvack.org [resent because I can't type] > vm.max_map_count I always thought it is some kind of algorithmic complexity limiter and kernel memory limiter. VMAs are under SLAB_ACCOUNT nowadays but ->mmap list stays: $ chgrep -e 'for.*vma = vma->vm_next' | wc -l 41 In particular readdir on /proc/*/map_files . I'm saying you can not simply remove this sysctl. -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753686AbdK0Tr6 (ORCPT ); Mon, 27 Nov 2017 14:47:58 -0500 Received: from mail-wr0-f176.google.com ([209.85.128.176]:40707 "EHLO mail-wr0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751673AbdK0Tr5 (ORCPT ); Mon, 27 Nov 2017 14:47:57 -0500 X-Google-Smtp-Source: AGs4zMYF6nF2zkqKMcEkIY2pT4cgxDz+sry6gAYCkwEr34mFNCV//0c8ImgqFls0SAFjnhneqq1grg== Date: Mon, 27 Nov 2017 22:47:53 +0300 From: Alexey Dobriyan To: mikpelinux@gmail.com Cc: linux-kernel@vger.kernel.org, mhocko@kernel.org, willy@infradead.org, ak@linux.intel.com, linux-mm@kvack.org Subject: Re: [PATCH] mm: disable `vm.max_map_count' sysctl limit Message-ID: <20171127194753.GB28115@avx2> References: <20171127194603.GA28115@avx2> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171127194603.GA28115@avx2> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [resent because I can't type] > vm.max_map_count I always thought it is some kind of algorithmic complexity limiter and kernel memory limiter. VMAs are under SLAB_ACCOUNT nowadays but ->mmap list stays: $ chgrep -e 'for.*vma = vma->vm_next' | wc -l 41 In particular readdir on /proc/*/map_files . I'm saying you can not simply remove this sysctl.