Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755537AbbHYRDX (ORCPT ); Tue, 25 Aug 2015 13:03:23 -0400 Received: from mail-ig0-f176.google.com ([209.85.213.176]:38473 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751315AbbHYRDW (ORCPT ); Tue, 25 Aug 2015 13:03:22 -0400 MIME-Version: 1.0 In-Reply-To: References: <20150823060443.GA9882@gmail.com> <20150823064603.14050.qmail@ns.horizon.com> <20150823081750.GA28349@gmail.com> <87h9npwtx3.fsf@rasmusvillemoes.dk> Date: Tue, 25 Aug 2015 10:03:21 -0700 X-Google-Sender-Auth: IOaZPeXgSECbp8r_Epd9I-7fkbI Message-ID: Subject: Re: [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info From: Linus Torvalds To: Rasmus Villemoes Cc: Ingo Molnar , George Spelvin , Dave Hansen , Linux Kernel Mailing List , linux-mm , Peter Zijlstra , Rik van Riel , David Rientjes Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 944 Lines: 22 On Tue, Aug 25, 2015 at 9:39 AM, Linus Torvalds wrote: > > I'm not convinced anybody actually uses those values, and they are > getting *less* relevant rather than more (on 64-bit, those values > really don't matter, since the vmalloc space isn't really a > limitation) Side note: the people who actually care about "my vmalloc area is too full, what's up?" would use /proc/vmallocinfo anyway, since that's what shows things like fragmentation etc. So I'm just talking about removing the /proc/meminfo part. First try to remove it *all*, and if there is some script that hollers because it wants to parse them, print out the values as zero. Linus -- 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/