linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Joe Lawrence <joe.lawrence@stratus.com>, Mel Gorman <mgorman@suse.de>
Cc: linux-mm@kvack.org
Subject: Re: numa balancing stuck in task_work_run
Date: Fri, 25 Sep 2015 13:38:48 -0400	[thread overview]
Message-ID: <560586A8.4060901@redhat.com> (raw)
In-Reply-To: <560583F9.4040908@stratus.com>

On 09/25/2015 01:27 PM, Joe Lawrence wrote:
> On 09/24/2015 09:04 PM, Rik van Riel wrote:
>> On 09/24/2015 05:14 PM, Joe Lawrence wrote:
>>> [ +cc for linux-mm mailinglist address ]
>>>
>>> On 09/24/2015 05:08 PM, Joe Lawrence wrote:
>>>> Hi Mel, Rik et al,
>>>>
>>>> We've encountered interesting NUMA balancing behavior on RHEL7.1,
>>>> reproduced with an upstream 4.2 kernel (of similar .config), that can
>>>> leave a user process trapped in the kernel performing task_numa_work.
>>>>
>>>> Our test group set up a server with 256GB memory running a program that
>>>> allocates and dirties ~50% of that memory.  They reported the following
>>>> condition when they attempted to kill the test process -- the signal was
>>>> never handled, instead traces showed the task stuck here:
>>
>> Does the bug still happen with this patch applied?
>>
>> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=4620f8c1fda2af4ccbd11e194e2dd785f7d7f279
>>
> 
> Hi Rik,
> 
> Success!  With 4620f8c1fda2 (-tip) cherry-picked on-top of 4.2, I could
> successfully kill off the memory test process, even when the
> numa_scan_period_max dropped to 140.
> 
> I also ran kicked off the est program and let continue overnight (it
> restarts itself after a given time) and several iterations ran without
> incident.

Glad to hear the issue is fixed in the latest -tip tree.

FWIW, that fix is also slated to show up in the next RHEL 7
update.

-- 
All rights reversed

--
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>

      reply	other threads:[~2015-09-25 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5604665D.3030504@stratus.com>
2015-09-24 21:14 ` numa balancing stuck in task_work_run Joe Lawrence
2015-09-25  1:04   ` Rik van Riel
2015-09-25 17:27     ` Joe Lawrence
2015-09-25 17:38       ` Rik van Riel [this message]

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=560586A8.4060901@redhat.com \
    --to=riel@redhat.com \
    --cc=joe.lawrence@stratus.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    /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).