From: Peter Zijlstra <peterz@infradead.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Alex Thorlton <athorlton@sgi.com>,
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: Tue, 14 Oct 2014 16:54:35 +0200 [thread overview]
Message-ID: <20141014145435.GA7369@worktop.fdxtended.com> (raw)
In-Reply-To: <20141014114828.GA6524@node.dhcp.inet.fi>
On Tue, Oct 14, 2014 at 02:48:28PM +0300, Kirill A. Shutemov wrote:
> Why whould you want to pin khugpeaged? Is there a valid use-case?
> Looks like userspace shoots to its leg.
Its just bad design to put so much work in another context. But the
use-case is isolating other cpus.
> Is there a reason why we should respect cpuset limitation for kernel
> threads?
Yes, because we want to allow isolating CPUs from 'random' activity.
> Should we bypass cpuset for PF_KTHREAD completely?
No. That'll break stuff.
--
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: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Alex Thorlton <athorlton@sgi.com>,
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: Tue, 14 Oct 2014 16:54:35 +0200 [thread overview]
Message-ID: <20141014145435.GA7369@worktop.fdxtended.com> (raw)
In-Reply-To: <20141014114828.GA6524@node.dhcp.inet.fi>
On Tue, Oct 14, 2014 at 02:48:28PM +0300, Kirill A. Shutemov wrote:
> Why whould you want to pin khugpeaged? Is there a valid use-case?
> Looks like userspace shoots to its leg.
Its just bad design to put so much work in another context. But the
use-case is isolating other cpus.
> Is there a reason why we should respect cpuset limitation for kernel
> threads?
Yes, because we want to allow isolating CPUs from 'random' activity.
> Should we bypass cpuset for PF_KTHREAD completely?
No. That'll break stuff.
next prev parent reply other threads:[~2014-10-14 14:54 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
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 [this message]
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=20141014145435.GA7369@worktop.fdxtended.com \
--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=kirill@shutemov.name \
--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.