From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm/thp: Always allocate transparent hugepages on local node
Date: Mon, 24 Nov 2014 17:03:42 +0200 [thread overview]
Message-ID: <20141124150342.GA3889@node.dhcp.inet.fi> (raw)
In-Reply-To: <1416838791-30023-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Mon, Nov 24, 2014 at 07:49:51PM +0530, Aneesh Kumar K.V wrote:
> This make sure that we try to allocate hugepages from local node. If
> we can't we fallback to small page allocation based on
> mempolicy. This is based on the observation that allocating pages
> on local node is more beneficial that allocating hugepages on remote node.
Local node on allocation is not necessary local node for use.
If policy says to use a specific node[s], we should follow.
I think it makes sense to force local allocation if policy is interleave
or if current node is in preferred or bind set.
--
Kirill A. Shutemov
--
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: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm/thp: Always allocate transparent hugepages on local node
Date: Mon, 24 Nov 2014 17:03:42 +0200 [thread overview]
Message-ID: <20141124150342.GA3889@node.dhcp.inet.fi> (raw)
In-Reply-To: <1416838791-30023-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Mon, Nov 24, 2014 at 07:49:51PM +0530, Aneesh Kumar K.V wrote:
> This make sure that we try to allocate hugepages from local node. If
> we can't we fallback to small page allocation based on
> mempolicy. This is based on the observation that allocating pages
> on local node is more beneficial that allocating hugepages on remote node.
Local node on allocation is not necessary local node for use.
If policy says to use a specific node[s], we should follow.
I think it makes sense to force local allocation if policy is interleave
or if current node is in preferred or bind set.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2014-11-24 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 14:19 [RFC PATCH] mm/thp: Always allocate transparent hugepages on local node Aneesh Kumar K.V
2014-11-24 14:19 ` Aneesh Kumar K.V
2014-11-24 15:03 ` Kirill A. Shutemov [this message]
2014-11-24 15:03 ` Kirill A. Shutemov
2014-11-24 21:33 ` David Rientjes
2014-11-24 21:33 ` David Rientjes
2014-11-25 14:17 ` Kirill A. Shutemov
2014-11-25 14:17 ` Kirill A. Shutemov
2014-11-27 6:32 ` Aneesh Kumar K.V
2014-11-27 6:32 ` Aneesh Kumar K.V
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=20141124150342.GA3889@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.