From: Waiman Long <llong@redhat.com>
To: Roman Gushchin <guro@fb.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Shakeel Butt <shakeelb@google.com>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 2/2] mm: memcg/slab: Create a new set of kmalloc-cg-<n> caches
Date: Wed, 5 May 2021 14:54:00 -0400 [thread overview]
Message-ID: <5d1683d2-1023-1d1c-91e7-b68549debe1d@redhat.com> (raw)
In-Reply-To: <f14a263b-10ea-ef2b-eefa-066591a4b637@redhat.com>
On 5/5/21 2:11 PM, Waiman Long wrote:
> On 5/5/21 1:30 PM, Roman Gushchin wrote:
>
>>
>> Btw, I wonder if we also need a change in the slab caches merging
>> procedure?
>> KMALLOC_NORMAL caches should not be merged with caches which can
>> potentially
>> include accounted objects.
>
> Thank for catching this omission.
>
> I will take a look and modify the merging procedure in a new patch.
> Accounting is usually specified at kmem_cache_create() time. Though, I
> did find one instance of setting ACCOUNT flag in kmem_cache_alloc(), I
> will ignore this case and merge accounted, but unreclaimable caches to
> KMALLOC_CGROUP.
In mm/slab_common.c:
#define SLAB_MERGE_SAME (SLAB_RECLAIM_ACCOUNT | SLAB_CACHE_DMA | \
SLAB_CACHE_DMA32 | SLAB_ACCOUNT)
struct kmem_cache *find_mergeable(unsigned int size, unsigned int align,
:
if ((flags & SLAB_MERGE_SAME) != (s->flags &
SLAB_MERGE_SAME))
continue;
By making sure kmalloc-cg-* has SLAB_ACCOUNT bit set, a kmemcache
created with with SLAB_ACCOUNT may merge with kmalloc-cg-* whereas one
without SLAB_ACCOUNT may merge with kmalloc-* for now. So the current
code should work fine for most cases. Though, if the ACCOUNT flag is set
at kmem_cache_alloc() and the cache happens to be merged into kmalloc-*,
we will have the rare case that an objcg pointer array may have to be
added to a kmalloc-* cache. However, this is not a common practice, and
the three cases (not one, sorry) that I found so far is in
arch/x86/kvm/x86.c: ctxt = kmem_cache_zalloc(x86_emulator_cache,
GFP_KERNEL_ACCOUNT);
fs/hostfs/hostfs_kern.c: hi =
kmem_cache_alloc(hostfs_inode_cache, GFP_KERNEL_ACCOUNT);
virt/kvm/kvm_main.c: vcpu = kmem_cache_zalloc(kvm_vcpu_cache,
GFP_KERNEL_ACCOUNT);
We will have to advise against doing that.
Cheers,
Longman
prev parent reply other threads:[~2021-05-05 18:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 15:46 [PATCH v3 0/2] mm: memcg/slab: Fix objcg pointer array handling problem Waiman Long
2021-05-05 15:46 ` [PATCH v3 1/2] mm: memcg/slab: Properly set up gfp flags for objcg pointer array Waiman Long
2021-05-05 16:09 ` Shakeel Butt
2021-05-05 16:46 ` Roman Gushchin
2021-05-05 15:46 ` [PATCH v3 2/2] mm: memcg/slab: Create a new set of kmalloc-cg-<n> caches Waiman Long
2021-05-05 16:06 ` Vlastimil Babka
2021-05-05 16:31 ` Waiman Long
2021-05-05 16:17 ` Shakeel Butt
2021-05-05 16:31 ` Waiman Long
2021-05-05 17:30 ` Roman Gushchin
2021-05-05 18:02 ` Vlastimil Babka
2021-05-05 18:18 ` Roman Gushchin
2021-05-05 18:31 ` Waiman Long
2021-05-05 18:38 ` Roman Gushchin
2021-05-05 18:56 ` Waiman Long
2021-05-05 18:32 ` Roman Gushchin
2021-05-05 21:29 ` Vlastimil Babka
2021-05-05 22:19 ` Roman Gushchin
2021-05-05 23:06 ` Waiman Long
2021-05-05 18:11 ` Waiman Long
2021-05-05 18:22 ` Roman Gushchin
2021-05-05 18:54 ` Waiman Long [this message]
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=5d1683d2-1023-1d1c-91e7-b68549debe1d@redhat.com \
--to=llong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
/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).