From: Yafang Shao <laoar.shao@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Linux MM <linux-mm@kvack.org>,
shaoyafang@didiglobal.com
Subject: Re: [PATCH] mm: compaction: remove unnecessary CONFIG_COMPACTION
Date: Tue, 26 Feb 2019 21:32:08 +0800 [thread overview]
Message-ID: <CALOAHbBBKbJqD4kGQzescyvEnzfxmZyNPvy-wEsGHLEt+KQtSA@mail.gmail.com> (raw)
In-Reply-To: <8622dd4e-6341-1ea2-0e26-ed7f6b2aaec4@suse.cz>
On Tue, Feb 26, 2019 at 8:32 PM Vlastimil Babka <vbabka@suse.cz> wrote:
>
> On 2/26/19 7:19 AM, Yafang Shao wrote:
> > The file trace/events/compaction.h is included only when
> > CONFIG_COMPACTION is defined, so it is unnecessary to use
> > CONFIG_COMPACTION again in this file.
>
> Are you sure? What about CONFIG_CMA?
>
Oops.
My bad. Sorry about the noise.
> #if defined CONFIG_COMPACTION || defined CONFIG_CMA
>
> #define CREATE_TRACE_POINTS
> #include <trace/events/compaction.h>
>
>
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > ---
> > include/trace/events/compaction.h | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> > diff --git a/include/trace/events/compaction.h b/include/trace/events/compaction.h
> > index 6074eff..06fb680 100644
> > --- a/include/trace/events/compaction.h
> > +++ b/include/trace/events/compaction.h
> > @@ -132,7 +132,6 @@
> > __entry->sync ? "sync" : "async")
> > );
> >
> > -#ifdef CONFIG_COMPACTION
> > TRACE_EVENT(mm_compaction_end,
> > TP_PROTO(unsigned long zone_start, unsigned long migrate_pfn,
> > unsigned long free_pfn, unsigned long zone_end, bool sync,
> > @@ -166,7 +165,6 @@
> > __entry->sync ? "sync" : "async",
> > __print_symbolic(__entry->status, COMPACTION_STATUS))
> > );
> > -#endif
> >
> > TRACE_EVENT(mm_compaction_try_to_compact_pages,
> >
> > @@ -195,7 +193,6 @@
> > __entry->prio)
> > );
> >
> > -#ifdef CONFIG_COMPACTION
> > DECLARE_EVENT_CLASS(mm_compaction_suitable_template,
> >
> > TP_PROTO(struct zone *zone,
> > @@ -296,7 +293,6 @@
> >
> > TP_ARGS(zone, order)
> > );
> > -#endif
> >
> > TRACE_EVENT(mm_compaction_kcompactd_sleep,
> >
> >
>
next prev parent reply other threads:[~2019-02-26 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 6:19 Yafang Shao
2019-02-26 12:32 ` Vlastimil Babka
2019-02-26 13:32 ` Yafang Shao [this message]
2019-02-26 14:31 ` kbuild test robot
2019-02-26 16:28 ` kbuild test robot
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=CALOAHbBBKbJqD4kGQzescyvEnzfxmZyNPvy-wEsGHLEt+KQtSA@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--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