From: Michal Hocko <mhocko@kernel.org>
To: Roman Gushchin <guro@fb.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH 1/3] mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES
Date: Fri, 13 Apr 2018 08:59:44 +0200 [thread overview]
Message-ID: <20180413065944.GE17484@dhcp22.suse.cz> (raw)
In-Reply-To: <20180412145702.GB30714@castle.DHCP.thefacebook.com>
On Thu 12-04-18 15:57:03, Roman Gushchin wrote:
> On Thu, Apr 12, 2018 at 08:52:52AM +0200, Vlastimil Babka wrote:
[...]
> > We would be just making the reported values more precise wrt reality.
>
> It depends on if we believe that only slab memory can be reclaimable
> or not. If yes, this is true, otherwise not.
>
> My guess is that some drivers (e.g. networking) might have buffers,
> which are reclaimable under mempressure, and are allocated using
> the page allocator. But I have to look closer...
Well, we have many direct page allocator users which are not accounted
in vmstat. Some of those use their specific accounting (e.g. network
buffers, some fs metadata a many others). In the ideal world MM layer
would know about those but...
Anyway, this particular case is quite clear, no? We _use_ kmalloc so
this is slab allocator. We just misaccount it.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-13 6:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 13:37 [PATCH 0/3] indirectly reclaimable memory Roman Gushchin
2018-03-05 13:37 ` [PATCH 1/3] mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES Roman Gushchin
2018-04-11 13:16 ` Vlastimil Babka
2018-04-11 13:56 ` Roman Gushchin
2018-04-12 6:52 ` Vlastimil Babka
2018-04-12 11:52 ` Michal Hocko
2018-04-12 14:38 ` Roman Gushchin
2018-04-12 14:46 ` Michal Hocko
2018-04-12 14:57 ` Roman Gushchin
2018-04-13 6:59 ` Michal Hocko [this message]
2018-04-13 12:13 ` vinayak menon
2018-04-25 3:49 ` Vijayanand Jitta
2018-04-25 12:52 ` Roman Gushchin
2018-04-25 15:47 ` Vlastimil Babka
2018-04-25 16:48 ` Roman Gushchin
2018-04-25 17:02 ` Vlastimil Babka
2018-04-25 17:23 ` Roman Gushchin
2018-04-25 15:55 ` Matthew Wilcox
2018-04-25 16:59 ` Vlastimil Babka
2018-03-05 13:37 ` [PATCH 2/3] mm: add indirectly reclaimable memory to MemAvailable Roman Gushchin
2018-03-05 13:47 ` Roman Gushchin
2018-03-05 13:37 ` [PATCH 2/3] mm: treat indirectly reclaimable memory as available in MemAvailable Roman Gushchin
2018-03-05 13:37 ` [PATCH 3/3] dcache: account external names as indirectly reclaimable memory Roman Gushchin
2018-03-12 21:17 ` Al Viro
2018-03-12 22:36 ` Roman Gushchin
2018-03-13 0:45 ` Al Viro
2018-04-05 22:11 ` Andrew Morton
2018-04-06 10:32 ` Roman Gushchin
2018-04-13 13:35 ` Minchan Kim
2018-04-13 13:59 ` Michal Hocko
2018-04-13 14:20 ` Vlastimil Babka
2018-04-13 14:28 ` Michal Hocko
2018-04-13 14:37 ` Johannes Weiner
2018-04-16 11:41 ` Michal Hocko
2018-04-16 12:06 ` Vlastimil Babka
2018-04-16 12:27 ` Michal Hocko
2018-04-16 19:57 ` Vlastimil Babka
2018-04-17 6:44 ` Michal Hocko
2018-04-16 13:09 ` Matthew Wilcox
2018-04-17 11:24 ` Roman Gushchin
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=20180413065944.GE17484@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).