[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <860c4f66-0327-4fd0-bd49-5be742c6931d@suse.cz>
Date: Sun, 1 Sep 2024 21:34:44 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Muchun Song <muchun.song@...ux.dev>, David Rientjes <rientjes@...gle.com>,
Hyeonggon Yoo <42.hyeyoo@...il.com>, Eric Dumazet <edumazet@...gle.com>,
"David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Meta kernel team <kernel-team@...a.com>,
cgroups@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v3] memcg: add charging of already allocated slab objects
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
Powered by blists - more mailing lists