All of lore.kernel.org
 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: Thu, 24 Sep 2015 21:04:23 -0400	[thread overview]
Message-ID: <56049D97.6080106@redhat.com> (raw)
In-Reply-To: <560467B8.6000101@stratus.com>

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

-- 
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  1:04 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 [this message]
2015-09-25 17:27     ` Joe Lawrence
2015-09-25 17:38       ` Rik van Riel

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=56049D97.6080106@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 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.