From: Yafang Shao <laoar.shao@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Souptick Joarder <jrdr.linux@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
shaoyafang@didiglobal.com
Subject: Re: [PATCH] mm: vmscan: show zone type in kswapd tracepoints
Date: Tue, 12 Mar 2019 19:04:43 +0800 [thread overview]
Message-ID: <CALOAHbDHM1mJ3X9x3vFpDagd81T+hrb7_xdqM12x6JQXuHqwxA@mail.gmail.com> (raw)
In-Reply-To: <20190311084743.GX5232@dhcp22.suse.cz>
On Mon, Mar 11, 2019 at 4:47 PM Michal Hocko <mhocko@kernel.org> wrote:
>
> On Fri 01-03-19 15:38:54, Yafang Shao wrote:
> > If we want to know the zone type, we have to check whether
> > CONFIG_ZONE_DMA, CONFIG_ZONE_DMA32 and CONFIG_HIGHMEM are set or not,
> > that's not so convenient.
> >
> > We'd better show the zone type directly.
>
> I do agree that zone number is quite PITA to process in general but do
> we really need this information in the first place? Why do we even care?
>
Sometimes we want to know this event occurs in which zone, then we can
get the information of this zone,
for example via /proc/zoneinfo.
It could give us more information for debugging.
> Zones are an MM internal implementation details and the more we export
> to the userspace the more we are going to argue about breaking userspace
> when touching them. So I would rather not export that information unless
> it is terribly useful.
>
I 'm not sure whether zone type is terribly useful or not, but the
'zid' is useless at all.
I don't agree that Zones are MM internal.
We can get the zone type in many ways, for example /proc/zoneinfo.
If we show this event occurs in which zone, we'd better show the zone type,
or we should drop this 'zid'.
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > ---
> > include/trace/events/vmscan.h | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/trace/events/vmscan.h b/include/trace/events/vmscan.h
> > index a1cb913..4c8880b 100644
> > --- a/include/trace/events/vmscan.h
> > +++ b/include/trace/events/vmscan.h
> > @@ -73,7 +73,10 @@
> > __entry->order = order;
> > ),
> >
> > - TP_printk("nid=%d zid=%d order=%d", __entry->nid, __entry->zid, __entry->order)
> > + TP_printk("nid=%d zid=%-8s order=%d",
> > + __entry->nid,
> > + __print_symbolic(__entry->zid, ZONE_TYPE),
> > + __entry->order)
> > );
> >
> > TRACE_EVENT(mm_vmscan_wakeup_kswapd,
> > @@ -96,9 +99,9 @@
> > __entry->gfp_flags = gfp_flags;
> > ),
> >
> > - TP_printk("nid=%d zid=%d order=%d gfp_flags=%s",
> > + TP_printk("nid=%d zid=%-8s order=%d gfp_flags=%s",
> > __entry->nid,
> > - __entry->zid,
> > + __print_symbolic(__entry->zid, ZONE_TYPE),
> > __entry->order,
> > show_gfp_flags(__entry->gfp_flags))
> > );
> > --
> > 1.8.3.1
> >
>
> --
> Michal Hocko
> SUSE Labs
next prev parent reply other threads:[~2019-03-12 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 7:38 Yafang Shao
2019-03-11 8:47 ` Michal Hocko
2019-03-12 11:04 ` Yafang Shao [this message]
2019-03-12 13:38 ` Michal Hocko
2019-03-12 14:10 ` Yafang Shao
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=CALOAHbDHM1mJ3X9x3vFpDagd81T+hrb7_xdqM12x6JQXuHqwxA@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shaoyafang@didiglobal.com \
--cc=vbabka@suse.cz \
/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