From: Vlastimil Babka <vbabka@suse.cz>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>, Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Linux-MM <linux-mm@kvack.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v4
Date: Thu, 1 Dec 2016 15:27:28 +0100 [thread overview]
Message-ID: <08b15992-a94e-1dc1-533c-16cdff7a2e8c@suse.cz> (raw)
In-Reply-To: <20161201142429.w6lazfn4g6ndpezl@techsingularity.net>
On 12/01/2016 03:24 PM, Mel Gorman wrote:
> On Thu, Dec 01, 2016 at 02:41:29PM +0100, Vlastimil Babka wrote:
>> On 12/01/2016 01:24 AM, Mel Gorman wrote:
>>
>> ...
>>
>>
>> Hmm I think that if this hits, we don't decrease count/increase nr_freed and
>> pcp->count will become wrong.
>
> Ok, I think you're right but I also think it's relatively trivial to fix
> with
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 94808f565f74..8777aefc1b8e 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1134,13 +1134,13 @@ static void free_pcppages_bulk(struct zone *zone, int count,
> if (unlikely(isolated_pageblocks))
> mt = get_pageblock_migratetype(page);
>
> + nr_freed += (1 << order);
> + count -= (1 << order);
> if (bulkfree_pcp_prepare(page))
> continue;
>
> __free_one_page(page, page_to_pfn(page), zone, order, mt);
> trace_mm_page_pcpu_drain(page, order, mt);
> - nr_freed += (1 << order);
> - count -= (1 << order);
> } while (count > 0 && --batch_free && !list_empty(list));
> }
> spin_unlock(&zone->lock);
>
>> And if we are unlucky/doing full drain, all
>> lists will get empty, but as count stays e.g. 1, we loop forever on the
>> outer while()?
>>
>
> Potentially yes. Granted the system is already in a bad state as pages
> are being freed in a bad or unknown state but we haven't halted the
> system for that in the past.
>
>> BTW, I think there's a similar problem (but not introduced by this patch) in
>> rmqueue_bulk() and its
>>
>> if (unlikely(check_pcp_refill(page)))
>> continue;
>>
>
> Potentially yes. It's outside the scope of this patch but it needs
> fixing.
>
> If you agree with the above fix, I'll roll it into a v5 and append
> another patch for this issue.
Yeah, looks fine. Thanks.
--
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>
next prev parent reply other threads:[~2016-12-01 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 0:24 [PATCH] mm: page_alloc: High-order per-cpu page allocator v4 Mel Gorman
2016-12-01 13:41 ` Vlastimil Babka
2016-12-01 14:24 ` Mel Gorman
2016-12-01 14:27 ` Vlastimil Babka [this message]
2016-12-01 13:42 ` Michal Hocko
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=08b15992-a94e-1dc1-533c-16cdff7a2e8c@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.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;
as well as URLs for NNTP newsgroup(s).