From: Hugh Dickins <hughd@google.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org
Subject: Re: [patch] mm, memcg: periodically schedule when emptying page list
Date: Mon, 2 Jun 2014 16:44:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1406021637170.5627@eggly.anvils> (raw)
In-Reply-To: <alpine.DEB.2.02.1406021612550.6487@chino.kir.corp.google.com>
On Mon, 2 Jun 2014, David Rientjes wrote:
> mem_cgroup_force_empty_list() can iterate a large number of pages on an lru and
> mem_cgroup_move_parent() doesn't return an errno unless certain criteria, none
> of which indicate that the iteration may be taking too long, is met.
>
> We have encountered the following stack trace many times indicating
> "need_resched set for > 51000020 ns (51 ticks) without schedule", for example:
>
> scheduler_tick()
> <timer irq>
> mem_cgroup_move_account+0x4d/0x1d5
> mem_cgroup_move_parent+0x8d/0x109
> mem_cgroup_reparent_charges+0x149/0x2ba
> mem_cgroup_css_offline+0xeb/0x11b
> cgroup_offline_fn+0x68/0x16b
> process_one_work+0x129/0x350
>
> If this iteration is taking too long, indicated by need_resched(), then
> periodically schedule and continue from where we last left off.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> mm/memcontrol.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -4764,6 +4764,7 @@ static void mem_cgroup_force_empty_list(struct mem_cgroup *memcg,
> do {
> struct page_cgroup *pc;
> struct page *page;
> + int ret;
>
> spin_lock_irqsave(&zone->lru_lock, flags);
> if (list_empty(list)) {
> @@ -4781,8 +4782,13 @@ static void mem_cgroup_force_empty_list(struct mem_cgroup *memcg,
>
> pc = lookup_page_cgroup(page);
>
> - if (mem_cgroup_move_parent(page, pc, memcg)) {
> - /* found lock contention or "pc" is obsolete. */
> + ret = mem_cgroup_move_parent(page, pc, memcg);
> + if (ret || need_resched()) {
> + /*
> + * Couldn't grab the page reference, isolate the page,
> + * there was a pc mismatch, or we simply need to
> + * schedule because this is taking too long.
> + */
> busy = page;
> cond_resched();
> } else
Why not just move that cond_resched() down below the if/else?
No need to test need_resched() separately, and this page is not busy.
Hugh
--
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:[~2014-06-02 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 23:13 David Rientjes
2014-06-02 23:44 ` Hugh Dickins [this message]
2014-06-02 23:48 ` David Rientjes
2014-06-03 0:01 ` Hugh Dickins
2014-06-03 0:51 ` [patch v2] " David Rientjes
2014-06-03 1:15 ` Johannes Weiner
2014-06-03 6:27 ` 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=alpine.LSU.2.11.1406021637170.5627@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.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