From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B60F4C433B4 for ; Wed, 21 Apr 2021 07:00:56 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 59C486102A for ; Wed, 21 Apr 2021 07:00:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 59C486102A Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id A79FA6B006C; Wed, 21 Apr 2021 03:00:55 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A29866B006E; Wed, 21 Apr 2021 03:00:55 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8F10E6B0070; Wed, 21 Apr 2021 03:00:55 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0063.hostedemail.com [216.40.44.63]) by kanga.kvack.org (Postfix) with ESMTP id 72B896B006C for ; Wed, 21 Apr 2021 03:00:55 -0400 (EDT) Received: from smtpin16.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 32D09181AEF1E for ; Wed, 21 Apr 2021 07:00:55 +0000 (UTC) X-FDA: 78055476870.16.AA4F2D6 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf27.hostedemail.com (Postfix) with ESMTP id 50C3C801AE4C for ; Wed, 21 Apr 2021 07:00:38 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1618988453; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zuMPGCEoFTBrQjlLesKTqICmVZBdzid0Et5b/N6s22c=; b=E6ft7IUyhTxpxdBZH5f2BrBH6YUmpujpSA14FpGqI76XXwBse38NPU7V9frIpjmQXPFMCP gFBCDWT2/wbJHlcHqeiKMCyPAGbYM0pqrKg11phxLg/FR7oo8nJBj7rTM9C2sxD1uszXqh gYOiJyBdDR8lAqozU2mpjI144QjeVWw= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 6EECAAD80; Wed, 21 Apr 2021 07:00:53 +0000 (UTC) Date: Wed, 21 Apr 2021 09:00:52 +0200 From: Michal Hocko To: Mike Rapoport Cc: Jonathan Corbet , Alexey Dobriyan , Andrew Morton , Eric Dumazet , Matthew Wilcox , Mike Rapoport , linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org Subject: Re: [PATCH v3] docs: proc.rst: meminfo: briefly describe gaps in memory accounting Message-ID: References: <20210421061127.1182723-1-rppt@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210421061127.1182723-1-rppt@kernel.org> X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 50C3C801AE4C X-Stat-Signature: 9pytfou3ipo166873ft5d3ni1pcqea6e Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf27; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1618988438-233988 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed 21-04-21 09:11:27, Mike Rapoport wrote: > From: Mike Rapoport > > Add a paragraph that explains that it may happen that the counters in > /proc/meminfo do not add up to the overall memory usage. > > Signed-off-by: Mike Rapoport Acked-by: Michal Hocko > --- > v3: > * Add sentense about counters overlap > * Use wording suggested by Matthew > > v2: Link: https://lore.kernel.org/lkml/20210420121354.1160437-1-rppt@kernel.org > * Add brief changelog > * Fix typo > * Update example about network memory usage according to Eric's comment at > > https://lore.kernel.org/lkml/CANn89iKprp7WYeZy4RRO5jHykprnSCcVBc7Tk14Ui_MA9OK7Fg@mail.gmail.com > > v1: Link: https://lore.kernel.org/lkml/20210420085105.1156640-1-rppt@kernel.org > Documentation/filesystems/proc.rst | 11 +++++++++-- > 1 file changed, 9 insertions(+), 2 deletions(-) > > diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst > index 48fbfc336ebf..0a07a5025571 100644 > --- a/Documentation/filesystems/proc.rst > +++ b/Documentation/filesystems/proc.rst > @@ -929,8 +929,15 @@ meminfo > ~~~~~~~ > > Provides information about distribution and utilization of memory. This > -varies by architecture and compile options. The following is from a > -16GB PIII, which has highmem enabled. You may not have all of these fields. > +varies by architecture and compile options. Some of the counters reported > +here overlap. The memory reported by the non overlapping counters may not > +add up to the overall memory usage and the difference for some workloads > +can be substantial. In many cases there are other means to find out > +additional memory using subsystem specific interfaces, for instance > +/proc/net/sockstat for TCP memory allocations. > + > +The following is from a 16GB PIII, which has highmem enabled. > +You may not have all of these fields. > > :: > > -- > 2.29.2 > -- Michal Hocko SUSE Labs