linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, shaoyafang@didiglobal.com
Subject: Re: [PATCH] mm: vmscan: drop zone id from kswapd tracepoints
Date: Wed, 13 Mar 2019 09:03:54 +0100	[thread overview]
Message-ID: <20190313080354.GH5721@dhcp22.suse.cz> (raw)
In-Reply-To: <1552451813-10833-1-git-send-email-laoar.shao@gmail.com>

On Wed 13-03-19 12:36:53, Yafang Shao wrote:
> The zid is meaningless to the user.

This is quite bold statement. We do not know whether that is useful.
Quite likely not. I would go with

"It is not clear how is the zone id useful in kswapd tracepoints and the
id itself is not really easy to process because it depends on the
configuration (available zones). Let's drop the id for now. If somebody
really needs that information the the zone name should be used instead."

> If we really want to expose it, we'd better expose the zone type
> (i.e. ZONE_NORMAL) intead of this number.
> Per discussion with Michal, seems this zid is not so userful in kswapd
> tracepoints, so we'd better drop it to avoid making noise.
> 
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>

Acked-by: Michal Hocko <mhocko@suse.com>

> ---
>  include/trace/events/vmscan.h | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/include/trace/events/vmscan.h b/include/trace/events/vmscan.h
> index a1cb913..d3f029f 100644
> --- a/include/trace/events/vmscan.h
> +++ b/include/trace/events/vmscan.h
> @@ -73,7 +73,9 @@
>  		__entry->order	= order;
>  	),
>  
> -	TP_printk("nid=%d zid=%d order=%d", __entry->nid, __entry->zid, __entry->order)
> +	TP_printk("nid=%d order=%d",
> +		__entry->nid,
> +		__entry->order)
>  );
>  
>  TRACE_EVENT(mm_vmscan_wakeup_kswapd,
> @@ -96,9 +98,8 @@
>  		__entry->gfp_flags	= gfp_flags;
>  	),
>  
> -	TP_printk("nid=%d zid=%d order=%d gfp_flags=%s",
> +	TP_printk("nid=%d order=%d gfp_flags=%s",
>  		__entry->nid,
> -		__entry->zid,
>  		__entry->order,
>  		show_gfp_flags(__entry->gfp_flags))
>  );
> -- 
> 1.8.3.1

-- 
Michal Hocko
SUSE Labs


  reply	other threads:[~2019-03-13  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  4:36 Yafang Shao
2019-03-13  8:03 ` Michal Hocko [this message]
2019-03-13  8:38   ` 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=20190313080354.GH5721@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=shaoyafang@didiglobal.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