From: Michal Hocko <mhocko@suse.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Mike Rapoport <rppt@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Mike Rapoport <rppt@linux.ibm.com>,
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 v2] docs: proc.rst: meminfo: briefly describe gaps in memory accounting
Date: Wed, 21 Apr 2021 08:35:06 +0200 [thread overview]
Message-ID: <YH/HmtmZfBhtBlFK@dhcp22.suse.cz> (raw)
In-Reply-To: <YH8WYJU2Jk6S9YIJ@localhost.localdomain>
On Tue 20-04-21 20:58:56, Alexey Dobriyan wrote:
> On Tue, Apr 20, 2021 at 03:57:07PM +0200, Michal Hocko wrote:
> > On Tue 20-04-21 14:24:30, Matthew Wilcox wrote:
> > > On Tue, Apr 20, 2021 at 03:13:54PM +0300, Mike Rapoport wrote:
> > > > Add a paragraph that explains that it may happen that the counters in
> > > > /proc/meminfo do not add up to the overall memory usage.
> > >
> > > ... that is, the sum may be lower because memory is allocated for other
> > > purposes that is not reported here, right?
> >
> > yes. Many direct page allocator users are not accounted in any of the
> > existing counters.
>
> Does virtio_balloon dereserve special mention?
Yes
> From inside VM memory borrowing looks like one giant memory leak resulting
> in support tickets (not that people who file them read internal kernel
> documentation...)
Even if people do not read that documentation it is really good to have
a reference you can send when you are dealing with bug reports.
Thanks!
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-04-21 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 12:13 Mike Rapoport
2021-04-20 12:21 ` Mike Rapoport
2021-04-20 13:12 ` Michal Hocko
2021-04-20 13:24 ` Matthew Wilcox
2021-04-20 13:57 ` Michal Hocko
2021-04-20 14:05 ` Michal Hocko
2021-04-20 17:58 ` Alexey Dobriyan
2021-04-21 6:35 ` Michal Hocko [this message]
2021-04-20 14:51 ` Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YH/HmtmZfBhtBlFK@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox