All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice)
Date: Wed, 1 Jun 2016 10:19:21 +0100	[thread overview]
Message-ID: <20160601091921.GT2527@techsingularity.net> (raw)
In-Reply-To: <574E05B8.3060009@suse.cz>

On Tue, May 31, 2016 at 11:44:24PM +0200, Vlastimil Babka wrote:
> On 05/30/2016 05:56 PM, Mel Gorman wrote:
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index dba8cfd0b2d6..f2c1e47adc11 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -3232,6 +3232,9 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
> >  		 * allocations are system rather than user orientated
> >  		 */
> >  		ac->zonelist = node_zonelist(numa_node_id(), gfp_mask);
> > +		ac->preferred_zoneref = first_zones_zonelist(ac->zonelist,
> > +					ac->high_zoneidx, ac->nodemask);
> > +		ac->classzone_idx = zonelist_zone_idx(ac->preferred_zoneref);
> >  		page = get_page_from_freelist(gfp_mask, order,
> >  						ALLOC_NO_WATERMARKS, ac);
> >  		if (page)
> > 
> 
> Even if that didn't help for this report, I think it's needed too
> (except the classzone_idx which doesn't exist anymore?).
> 
> And I think the following as well. (the changed comment could be also
> just deleted).
> 

Why?

The comment is fine but I do not see why the recalculation would occur.

In the original code, the preferred_zoneref for statistics is calculated
based on either the supplied nodemask or cpuset_current_mems_allowed during
the initial attempt. It then relies on the cpuset checks in the slowpath
to encorce mems_allowed but the preferred zone doesn't change.

With your proposed change, it's possible that the
preferred_zoneref recalculation points to a zoneref disallowed by
cpuset_current_mems_sllowed. While it'll be skipped during allocation,
the statistics will still be against a zone that is potentially outside
what is allowed.

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@techsingularity.net>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice)
Date: Wed, 1 Jun 2016 10:19:21 +0100	[thread overview]
Message-ID: <20160601091921.GT2527@techsingularity.net> (raw)
In-Reply-To: <574E05B8.3060009@suse.cz>

On Tue, May 31, 2016 at 11:44:24PM +0200, Vlastimil Babka wrote:
> On 05/30/2016 05:56 PM, Mel Gorman wrote:
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index dba8cfd0b2d6..f2c1e47adc11 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -3232,6 +3232,9 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
> >  		 * allocations are system rather than user orientated
> >  		 */
> >  		ac->zonelist = node_zonelist(numa_node_id(), gfp_mask);
> > +		ac->preferred_zoneref = first_zones_zonelist(ac->zonelist,
> > +					ac->high_zoneidx, ac->nodemask);
> > +		ac->classzone_idx = zonelist_zone_idx(ac->preferred_zoneref);
> >  		page = get_page_from_freelist(gfp_mask, order,
> >  						ALLOC_NO_WATERMARKS, ac);
> >  		if (page)
> > 
> 
> Even if that didn't help for this report, I think it's needed too
> (except the classzone_idx which doesn't exist anymore?).
> 
> And I think the following as well. (the changed comment could be also
> just deleted).
> 

Why?

The comment is fine but I do not see why the recalculation would occur.

In the original code, the preferred_zoneref for statistics is calculated
based on either the supplied nodemask or cpuset_current_mems_allowed during
the initial attempt. It then relies on the cpuset checks in the slowpath
to encorce mems_allowed but the preferred zone doesn't change.

With your proposed change, it's possible that the
preferred_zoneref recalculation points to a zoneref disallowed by
cpuset_current_mems_sllowed. While it'll be skipped during allocation,
the statistics will still be against a zone that is potentially outside
what is allowed.

-- 
Mel Gorman
SUSE Labs

  reply	other threads:[~2016-06-01  9:19 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 13:13 BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice) Geert Uytterhoeven
2016-05-30 13:13 ` Geert Uytterhoeven
2016-05-30 15:56 ` Mel Gorman
2016-05-30 15:56 ` Mel Gorman
2016-05-30 15:56   ` Mel Gorman
2016-05-30 17:37   ` Geert Uytterhoeven
2016-05-30 17:37     ` Geert Uytterhoeven
2016-05-30 17:37     ` Geert Uytterhoeven
2016-05-30 18:56     ` Mel Gorman
2016-05-30 18:56     ` Mel Gorman
2016-05-30 18:56       ` Mel Gorman
2016-05-31  9:28       ` Geert Uytterhoeven
2016-05-31  9:28         ` Geert Uytterhoeven
2016-05-31 10:13         ` Mel Gorman
2016-05-31 10:13           ` Mel Gorman
2016-05-31 10:13           ` Mel Gorman
2016-05-31  9:28       ` Geert Uytterhoeven
2016-05-31 21:44   ` Vlastimil Babka
2016-05-31 21:44     ` Vlastimil Babka
2016-06-01  9:19     ` Mel Gorman [this message]
2016-06-01  9:19       ` Mel Gorman
2016-06-01 10:01       ` BUG: scheduling while atomic: cron/668/0x10c9a0c0 Vlastimil Babka
2016-06-01 10:01       ` Vlastimil Babka
2016-06-01 10:01         ` Vlastimil Babka
2016-06-02 10:39         ` Mel Gorman
2016-06-02 10:39         ` Mel Gorman
2016-06-02 10:39           ` Mel Gorman
2016-06-02 12:04           ` Vlastimil Babka
2016-06-02 12:04             ` Vlastimil Babka
2016-06-02 12:04             ` Vlastimil Babka
2016-06-02 12:19             ` Mel Gorman
2016-06-02 12:19               ` Mel Gorman
2016-06-02 12:19               ` Mel Gorman
2016-06-02 18:43               ` Andrew Morton
2016-06-02 18:43                 ` Andrew Morton
2016-06-03  3:52                 ` Stephen Rothwell
2016-06-03  3:52                   ` Stephen Rothwell
2016-06-03  7:57                 ` Geert Uytterhoeven
2016-06-03  7:57                   ` Geert Uytterhoeven
2016-06-03  8:41                   ` Mel Gorman
2016-06-03  8:41                     ` Mel Gorman
2016-06-03  9:00                     ` Geert Uytterhoeven
2016-06-03  9:00                       ` Geert Uytterhoeven
2016-06-03  9:00                       ` Geert Uytterhoeven
2016-06-03 16:35                       ` Andrew Morton
2016-06-03 16:35                         ` Andrew Morton
2016-06-03 16:46                         ` Mel Gorman
2016-06-03 16:46                           ` Mel Gorman
2016-06-03 16:49                           ` Andrew Morton
2016-06-03 16:49                             ` Andrew Morton
2016-06-01  9:19     ` BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice) Mel Gorman
2016-05-31 21:44   ` Vlastimil Babka
  -- strict thread matches above, loose matches on Subject: below --
2016-05-30 13:13 Geert Uytterhoeven

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=20160601091921.GT2527@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mm@kvack.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.