From: Vlastimil Babka <vbabka@suse.cz>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
David Rientjes <rientjes@google.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>,
cgroups@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3] memcg: add charging of already allocated slab objects
Date: Sun, 1 Sep 2024 21:34:44 +0200 [thread overview]
Message-ID: <860c4f66-0327-4fd0-bd49-5be742c6931d@suse.cz> (raw)
In-Reply-To: <ukrl43rakgdzlo4fvw3ldwyoke76dgnseobtf75ldghe3fadxc@ag2y4jk77js2>
On 8/30/24 21:44, Shakeel Butt wrote:
>>
>> Also one thing:
>>
>> We should add some kernel doc for this, no? Explaining when people are
>> supposed to use this, that objects from KMALLOC_NORMAL will be ignored, and
>> what the return value means (including where it's faked to be true).
>>
>
> Yes this makes sense. I will add this info similar to the kmalloc()
> have. Should I send a v4 with this details?
Yeah please, will replace v3 with that.
Thanks
prev parent reply other threads:[~2024-09-01 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 17:53 Shakeel Butt
2024-08-30 9:07 ` Vlastimil Babka
2024-08-30 19:44 ` Shakeel Butt
2024-09-01 19:34 ` Vlastimil Babka [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=860c4f66-0327-4fd0-bd49-5be742c6931d@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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