From: Matthew Wilcox <willy@infradead.org>
To: Roman Gushchin <guro@fb.com>
Cc: Shakeel Butt <shakeelb@google.com>,
Vasily Averin <vvs@virtuozzo.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: tools/cgroup/memcg_slabinfo.py is broken
Date: Mon, 21 Feb 2022 13:27:23 +0000 [thread overview]
Message-ID: <YhOTO/pycEA6IKX5@casper.infradead.org> (raw)
In-Reply-To: <Yg2cKKnIboNu7j+p@carbon.DHCP.thefacebook.com>
On Wed, Feb 16, 2022 at 04:51:52PM -0800, Roman Gushchin wrote:
> >From 04efbbdcfde4535c4623f2fd6910a505a9c638bb Mon Sep 17 00:00:00 2001
> From: Roman Gushchin <guro@fb.com>
> Date: Wed, 16 Feb 2022 12:43:30 -0800
> Subject: [PATCH v2] tools/cgroup/slabinfo: update to work with struct slab
>
> After the introduction of the dedicated struct slab to describe slab
> pages by commit d122019bf061 ("mm: Split slab into its own type") and
> the following removal of the corresponding struct page's fields by
> commit 07f910f9b729 ("mm: Remove slab from struct page") the
[...]
>
> v2: change naming and count_partial()/count_free()/for_each_slab()
> signatures to work with slabs, suggested by Matthew Wilcox
>
> Signed-off-by: Roman Gushchin <guro@fb.com>
> Reported-by: Vasily Averin <vvs@virtuozzo.com>
Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
prev parent reply other threads:[~2022-02-21 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 13:22 Vasily Averin
2022-02-15 23:29 ` Roman Gushchin
[not found] ` <35486a00-791c-3b1b-14e0-476e6242709b@virtuozzo.com>
[not found] ` <Yg1kFH3umdrvOhu1@carbon.dhcp.thefacebook.com>
2022-02-16 21:12 ` Matthew Wilcox
2022-02-16 21:44 ` Roman Gushchin
[not found] ` <Yg1y0ax5bnjGLAqz@casper.infradead.org>
[not found] ` <Yg16ClVQj8SLSlqV@carbon.DHCP.thefacebook.com>
2022-02-16 23:12 ` Matthew Wilcox
2022-02-16 23:57 ` Shakeel Butt
2022-02-17 0:13 ` Matthew Wilcox
2022-02-17 0:25 ` Roman Gushchin
[not found] ` <Yg2cKKnIboNu7j+p@carbon.DHCP.thefacebook.com>
[not found] ` <11060a75-98c2-f547-68eb-fcab404a2539@virtuozzo.com>
2022-02-21 9:19 ` Vlastimil Babka
2022-02-21 13:27 ` Matthew Wilcox [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=YhOTO/pycEA6IKX5@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=linux-mm@kvack.org \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=vvs@virtuozzo.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