From: Peter Zijlstra <peterz@infradead.org>
To: Alex Thorlton <athorlton@sgi.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>, Bob Liu <lliubbo@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org
Subject: Re: [BUG] mm, thp: khugepaged can't allocate on requested node when confined to a cpuset
Date: Fri, 10 Oct 2014 11:20:52 +0200 [thread overview]
Message-ID: <20141010092052.GU4750@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141008191050.GK3778@sgi.com>
On Wed, Oct 08, 2014 at 02:10:50PM -0500, Alex Thorlton wrote:
> Is this particular bug a known issue?
Its not unexpected for me.
> I've been trying to come up with
> a simple way to fix the bug, but it's a bit difficult since we no longer
> have a way to trace back to the task_struct that we're collapsing for
> once we've reached get_page_from_freelist. I'm wondering if we might
> want to make the cpuset check higher up in the call-chain and then pass
> that nodemask down instead of sending a NULL nodemask, as we end up
> doing in many (most?) situations. I can think of several problems with
> that approach as well, but it's all I've come up with so far.
>
> The obvious workaround is to not isolate khugepaged to a cpuset, but
> since we're allowed to do so, I think the thread should probably behave
> appropriately when pinned to a cpuset.
>
> Any input on this issue is greatly appreciated. Thanks, guys!
So for the numa thing we do everything from the affected tasks context.
There was a lot of arguments early on that that could never really work,
but here we are.
Should we convert khugepaged to the same? Drive the whole thing from
task_work? That would make this issue naturally go away.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Alex Thorlton <athorlton@sgi.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>, Bob Liu <lliubbo@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org
Subject: Re: [BUG] mm, thp: khugepaged can't allocate on requested node when confined to a cpuset
Date: Fri, 10 Oct 2014 11:20:52 +0200 [thread overview]
Message-ID: <20141010092052.GU4750@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141008191050.GK3778@sgi.com>
On Wed, Oct 08, 2014 at 02:10:50PM -0500, Alex Thorlton wrote:
> Is this particular bug a known issue?
Its not unexpected for me.
> I've been trying to come up with
> a simple way to fix the bug, but it's a bit difficult since we no longer
> have a way to trace back to the task_struct that we're collapsing for
> once we've reached get_page_from_freelist. I'm wondering if we might
> want to make the cpuset check higher up in the call-chain and then pass
> that nodemask down instead of sending a NULL nodemask, as we end up
> doing in many (most?) situations. I can think of several problems with
> that approach as well, but it's all I've come up with so far.
>
> The obvious workaround is to not isolate khugepaged to a cpuset, but
> since we're allowed to do so, I think the thread should probably behave
> appropriately when pinned to a cpuset.
>
> Any input on this issue is greatly appreciated. Thanks, guys!
So for the numa thing we do everything from the affected tasks context.
There was a lot of arguments early on that that could never really work,
but here we are.
Should we convert khugepaged to the same? Drive the whole thing from
task_work? That would make this issue naturally go away.
next prev parent reply other threads:[~2014-10-10 9:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 19:10 [BUG] mm, thp: khugepaged can't allocate on requested node when confined to a cpuset Alex Thorlton
2014-10-08 19:10 ` Alex Thorlton
2014-10-10 9:20 ` Peter Zijlstra [this message]
2014-10-10 9:20 ` Peter Zijlstra
2014-10-10 18:56 ` Alex Thorlton
2014-10-10 18:56 ` Alex Thorlton
2014-10-10 21:57 ` Vlastimil Babka
2014-10-10 21:57 ` Vlastimil Babka
2014-10-14 14:58 ` Alex Thorlton
2014-10-14 14:58 ` Alex Thorlton
2014-10-21 10:59 ` Peter Zijlstra
2014-10-21 10:59 ` Peter Zijlstra
2014-10-21 10:55 ` Peter Zijlstra
2014-10-21 10:55 ` Peter Zijlstra
2014-10-21 16:25 ` Alex Thorlton
2014-10-21 16:25 ` Alex Thorlton
2014-10-14 11:48 ` Kirill A. Shutemov
2014-10-14 11:48 ` Kirill A. Shutemov
2014-10-14 14:54 ` Peter Zijlstra
2014-10-14 14:54 ` Peter Zijlstra
2014-10-14 15:31 ` Rik van Riel
2014-10-14 15:31 ` Rik van Riel
2014-10-14 17:38 ` Kirill A. Shutemov
2014-10-14 17:38 ` Kirill A. Shutemov
2014-10-21 10:17 ` Peter Zijlstra
2014-10-21 10:17 ` Peter Zijlstra
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=20141010092052.GU4750@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@redhat.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 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.