linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yafang Shao <laoar.shao@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Michal Hocko <mhocko@suse.com>,
	mgorman@techsingularity.net,
	 Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>,
	 shaoyafang@didiglobal.com
Subject: Re: [PATCH] mm/compaction: fix missed direct_compaction setting for non-direct compaction
Date: Fri, 29 Mar 2019 16:48:32 +0800	[thread overview]
Message-ID: <CALOAHbC7PqQ7UMm5Az=BAz9_hppYMWgNvxhq7EhqOkX0rWuQCA@mail.gmail.com> (raw)
In-Reply-To: <60f6a5fd-e4d3-b615-6f41-cc7dd16d183c@suse.cz>

On Fri, Mar 29, 2019 at 4:45 PM Vlastimil Babka <vbabka@suse.cz> wrote:
>
> On 3/29/19 9:36 AM, Yafang Shao wrote:
> > direct_compaction is not initialized for kcompactd or manually triggered
> > compaction (via /proc or /sys).
>
> It doesn't need to, this style of initialization does guarantee that any
> field not explicitly mentioned is initialized to 0/NULL/false... and
> this pattern is used all over the kernel.
>

Hmm.
You mean the gcc will set the local variable to 0 ?
Are there any reference to this behavior ?

Thanks
Yafang

> > That may cause unexpected behavior in __compact_finished(), so we should
> > set direct_compaction to false explicitly for these compactions.
>
> It's not necessary.
>
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > Cc: Vlastimil Babka <vbabka@suse.cz>
> > ---
> >  mm/compaction.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/compaction.c b/mm/compaction.c
> > index 98f99f4..ba2b711 100644
> > --- a/mm/compaction.c
> > +++ b/mm/compaction.c
> > @@ -2400,13 +2400,12 @@ static void compact_node(int nid)
> >               .total_free_scanned = 0,
> >               .mode = MIGRATE_SYNC,
> >               .ignore_skip_hint = true,
> > +             .direct_compaction = false,
> >               .whole_zone = true,
> >               .gfp_mask = GFP_KERNEL,
> >       };
> >
> > -
> >       for (zoneid = 0; zoneid < MAX_NR_ZONES; zoneid++) {
> > -
> >               zone = &pgdat->node_zones[zoneid];
> >               if (!populated_zone(zone))
> >                       continue;
> > @@ -2522,8 +2521,10 @@ static void kcompactd_do_work(pg_data_t *pgdat)
> >               .classzone_idx = pgdat->kcompactd_classzone_idx,
> >               .mode = MIGRATE_SYNC_LIGHT,
> >               .ignore_skip_hint = false,
> > +             .direct_compaction = false,
> >               .gfp_mask = GFP_KERNEL,
> >       };
> > +
> >       trace_mm_compaction_kcompactd_wake(pgdat->node_id, cc.order,
> >                                                       cc.classzone_idx);
> >       count_compact_event(KCOMPACTD_WAKE);
> >
>


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  8:36 Yafang Shao
2019-03-29  8:45 ` Vlastimil Babka
2019-03-29  8:48   ` Yafang Shao [this message]
2019-03-29  8:54     ` Vlastimil Babka
2019-03-29  8:55       ` 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='CALOAHbC7PqQ7UMm5Az=BAz9_hppYMWgNvxhq7EhqOkX0rWuQCA@mail.gmail.com' \
    --to=laoar.shao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --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