linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: akpm@linux-foundation.org
Cc: aarcange@redhat.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Fix NUMA problems in transparent hugepages and KSM
Date: Wed,  2 Mar 2011 16:45:20 -0800	[thread overview]
Message-ID: <1299113128-11349-1-git-send-email-andi@firstfloor.org> (raw)

[Updated version, mainly for integrating Andrea's fixes.
This should be ready for merge now. At least the core
bug fixes for hugepaged I would like to see in 38.]

The current transparent hugepages daemon can mess up local
memory affinity on NUMA systems. When it copies memory to a 
huge page it does not necessarily keep it on the same
node as the local allocations.

While fixing this I also found some more related issues:
- The NUMA policy interleaving for THP was using the small
page size, not the large parse size.
- KSM and THP copies also did not preserve the local node
- The accounting for local/remote allocations in the daemon
was misleading.
- There were no VM statistics counters for THP, which made it 
impossible to analyze.
 
At least some of the bug fixes are 2.6.38 candidates IMHO
because some of the NUMA problems are pretty bad. In some workloads
this can cause performance problems. 

What can be delayed are GFP_OTHERNODE and the statistics changes.

Git tree:

  git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc-2.6.git thp-numa

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2011-03-03  0:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  0:45 Andi Kleen [this message]
2011-03-03  0:45 ` [PATCH 1/8] Fix interleaving for transparent hugepages v2 Andi Kleen
2011-03-03  2:12   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 2/8] Change alloc_pages_vma to pass down the policy node for local policy Andi Kleen
2011-03-03  2:14   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 3/8] Add alloc_page_vma_node Andi Kleen
2011-03-03  2:15   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 4/8] Preserve original node for transparent huge page copies Andi Kleen
2011-03-03  2:17   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 5/8] Use correct numa policy node for transparent hugepages Andi Kleen
2011-03-03  2:26   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 6/8] Add __GFP_OTHER_NODE flag Andi Kleen
2011-03-03  2:33   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 7/8] Use GFP_OTHER_NODE for transparent huge pages Andi Kleen
2011-03-03  2:35   ` KAMEZAWA Hiroyuki
2011-03-03  0:45 ` [PATCH 8/8] Add VM counters for transparent hugepages Andi Kleen
2011-03-03  9:18   ` Johannes Weiner
2011-03-03 18:09     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2011-03-03 19:59 Fix NUMA problems in transparent hugepages and KSM Andi Kleen
2011-02-21 19:07 Andi Kleen

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=1299113128-11349-1-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).