From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Vlastimil Babka <vbabka@suse.cz>, David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg Thelen <gthelen@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch v2 for-4.0] mm, thp: really limit transparent hugepage allocation to local node
Date: Tue, 05 May 2015 18:52:58 +0530 [thread overview]
Message-ID: <87oalzcg5p.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <55488994.8010303@suse.cz>
Vlastimil Babka <vbabka@suse.cz> writes:
> On 04/21/2015 09:31 AM, Aneesh Kumar K.V wrote:
>> Vlastimil Babka <vbabka@suse.cz> writes:
>>
>>> On 25.2.2015 22:24, David Rientjes wrote:
>>>>
>>>>> alloc_pages_preferred_node() variant, change the exact_node() variant to pass
>>>>> __GFP_THISNODE, and audit and adjust all callers accordingly.
>>>>>
....
...
>>> Right, we might be changing behavior not just for slab allocators, but
>>> also others using such
>>> combination of flags.
>>
>> Any update on this ? Did we reach a conclusion on how to go forward here
>> ?
>
> I believe David's later version was merged already. Or what exactly are
> you asking about?
When I checked last time I didn't find it. Hence I asked here. Now I
see that it got committed as 5265047ac30191ea24b16503165000c225f54feb
Thanks
-aneesh
--
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>
prev parent reply other threads:[~2015-05-05 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 22:24 [patch " David Rientjes
2015-02-24 23:24 ` [patch v2 " David Rientjes
2015-02-25 10:52 ` Vlastimil Babka
2015-02-25 21:24 ` David Rientjes
2015-02-25 23:55 ` Vlastimil Babka
2015-04-21 7:31 ` Aneesh Kumar K.V
2015-05-05 9:12 ` Vlastimil Babka
2015-05-05 13:22 ` Aneesh Kumar K.V [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=87oalzcg5p.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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