From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: 'Mel Gorman' <mgorman@techsingularity.net>,
'Andrew Morton' <akpm@linux-foundation.org>
Cc: 'Tejun Heo' <tj@kernel.org>, 'Vlastimil Babka' <vbabka@suse.cz>,
'Linux Kernel' <linux-kernel@vger.kernel.org>,
'Linux-MM' <linux-mm@kvack.org>,
'Jesper Dangaard Brouer' <brouer@redhat.com>
Subject: Re: [PATCH] mm, page_alloc: Use static global work_struct for draining per-cpu pages
Date: Wed, 25 Jan 2017 17:33:16 +0800 [thread overview]
Message-ID: <004201d276ee$0f20fd80$2d62f880$@alibaba-inc.com> (raw)
In-Reply-To: <20170125083038.rzb5f43nptmk7aed@techsingularity.net>
On Wednesday, January 25, 2017 4:31 PM Mel Gorman wrote:
>
> As suggested by Vlastimil Babka and Tejun Heo, this patch uses a static
> work_struct to co-ordinate the draining of per-cpu pages on the workqueue.
> Only one task can drain at a time but this is better than the previous
> scheme that allowed multiple tasks to send IPIs at a time.
>
> One consideration is whether parallel requests should synchronise against
> each other. This patch does not synchronise for a global drain as the common
> case for such callers is expected to be multiple parallel direct reclaimers
> competing for pages when the watermark is close to min. Draining the per-cpu
> list is unlikely to make much progress and serialising the drain is of
> dubious merit. Drains are synchonrised for callers such as memory hotplug
> and CMA that care about the drain being complete when the function returns.
>
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
> ---
Acked-by: Hillf Danton <hillf.zj@alibaba-inc.com>
--
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:[~2017-01-25 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 8:30 Mel Gorman
2017-01-25 9:24 ` Vlastimil Babka
2017-01-25 9:33 ` Hillf Danton [this message]
2017-01-26 0:08 ` Andrew Morton
2017-01-26 10:47 ` Mel Gorman
2017-01-26 19:21 ` Tejun Heo
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='004201d276ee$0f20fd80$2d62f880$@alibaba-inc.com' \
--to=hillf.zj@alibaba-inc.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox