From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrea Arcangeli <aarcange@redhat.com>,
Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/45] Automatic NUMA Balancing V7
Date: Mon, 10 Dec 2012 15:12:57 +0530 [thread overview]
Message-ID: <20121210094257.GB6348@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121210090730.GF1009@suse.de>
> >
> > Got a chance to run autonuma-benchmark on a 8 node, 64 core machine.
> > the results are as below. (for each kernel I ran 5 iterations of
> > autonuma-benchmark)
> >
>
> Thanks, a test of v10 would also be appreciated. The differences between
> V7 and V10 are small but do include a change in how migrate rate-limiting
> is handled. It is unlikely it'll make a difference to this test but I'd
> like to rule it out.
>
Yes, have queued it for testing. Will report on completion.
> > KernelVersion: 3.7.0-rc3-mainline_v37rc7()
Please read it as 3.7-rc3
>
> What kernel is this? The name begins with 3.7-rc3 but then says
> v37rc7. v37rc7 of what? I thought it might be v3.7-rc7 but it already said
> it's 3.7-rc3 so I'm confused. Would it be possible to base the tests on
> a similar baseline kernel such as 3.7.0-rc7 or 3.7.0-rc8? The
> balancenuma patches should apply and the autonuma patches can be taken
> from the mm-autonuma-v28fastr4-mels-rebase branch in
> git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux-balancenuma.git
>
Yes, for the next set of reports I have based autonuma branch on this
branch.
> Either way, the figures look bad. I'm trying to find a similar machine
> but initially at least I have not had much luck. Can you post the .config
> you used for balancenuma in case I can reproduce the problem on a 4-node
> machine please? Are all the nodes the same size?
>
No all nodes are not of same size
There are 6 32 GB nodes and 2 64 GB nodes.
Will post the balancenuma config along with results.
--
Thanks and Regards
Srikar
--
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: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrea Arcangeli <aarcange@redhat.com>,
Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/45] Automatic NUMA Balancing V7
Date: Mon, 10 Dec 2012 15:12:57 +0530 [thread overview]
Message-ID: <20121210094257.GB6348@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121210090730.GF1009@suse.de>
> >
> > Got a chance to run autonuma-benchmark on a 8 node, 64 core machine.
> > the results are as below. (for each kernel I ran 5 iterations of
> > autonuma-benchmark)
> >
>
> Thanks, a test of v10 would also be appreciated. The differences between
> V7 and V10 are small but do include a change in how migrate rate-limiting
> is handled. It is unlikely it'll make a difference to this test but I'd
> like to rule it out.
>
Yes, have queued it for testing. Will report on completion.
> > KernelVersion: 3.7.0-rc3-mainline_v37rc7()
Please read it as 3.7-rc3
>
> What kernel is this? The name begins with 3.7-rc3 but then says
> v37rc7. v37rc7 of what? I thought it might be v3.7-rc7 but it already said
> it's 3.7-rc3 so I'm confused. Would it be possible to base the tests on
> a similar baseline kernel such as 3.7.0-rc7 or 3.7.0-rc8? The
> balancenuma patches should apply and the autonuma patches can be taken
> from the mm-autonuma-v28fastr4-mels-rebase branch in
> git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux-balancenuma.git
>
Yes, for the next set of reports I have based autonuma branch on this
branch.
> Either way, the figures look bad. I'm trying to find a similar machine
> but initially at least I have not had much luck. Can you post the .config
> you used for balancenuma in case I can reproduce the problem on a 4-node
> machine please? Are all the nodes the same size?
>
No all nodes are not of same size
There are 6 32 GB nodes and 2 64 GB nodes.
Will post the balancenuma config along with results.
--
Thanks and Regards
Srikar
next prev parent reply other threads:[~2012-12-10 10:13 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 19:25 [PATCH 00/40] Automatic NUMA Balancing V5 Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 01/40] x86: mm: only do a local tlb flush in ptep_set_access_flags() Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 02/40] x86: mm: drop TLB flush from ptep_set_access_flags Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 20:56 ` Alan Cox
2012-11-22 20:56 ` Alan Cox
2012-11-23 9:09 ` Mel Gorman
2012-11-23 9:09 ` Mel Gorman
2012-11-23 9:53 ` Borislav Petkov
2012-11-23 9:53 ` Borislav Petkov
2012-11-22 19:25 ` [PATCH 03/40] mm,generic: only flush the local TLB in ptep_set_access_flags Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 04/40] x86/mm: Introduce pte_accessible() Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 05/40] mm: Only flush the TLB when clearing an accessible pte Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 06/40] mm: Count the number of pages affected in change_protection() Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 07/40] mm: Optimize the TLB flush of sys_mprotect() and change_protection() users Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 08/40] mm: compaction: Move migration fail/success stats to migrate.c Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 09/40] mm: migrate: Add a tracepoint for migrate_pages Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 10/40] mm: compaction: Add scanned and isolated counters for compaction Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 11/40] mm: numa: define _PAGE_NUMA Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 12/40] mm: numa: pte_numa() and pmd_numa() Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 13/40] mm: numa: Support NUMA hinting page faults from gup/gup_fast Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 14/40] mm: numa: split_huge_page: transfer the NUMA type from the pmd to the pte Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 15/40] mm: numa: Create basic numa page hinting infrastructure Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 16/40] mm: mempolicy: Make MPOL_LOCAL a real policy Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 17/40] mm: mempolicy: Add MPOL_MF_NOOP Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 18/40] mm: mempolicy: Check for misplaced page Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 19/40] mm: migrate: Introduce migrate_misplaced_page() Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 20/40] mm: mempolicy: Use _PAGE_NUMA to migrate pages Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 21/40] mm: mempolicy: Add MPOL_MF_LAZY Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 22/40] mm: mempolicy: Implement change_prot_numa() in terms of change_protection() Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 23/40] mm: mempolicy: Hide MPOL_NOOP and MPOL_MF_LAZY from userspace for now Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 24/40] mm: numa: Add fault driven placement and migration Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 25/40] mm: sched: numa: Implement constant, per task Working Set Sampling (WSS) rate Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 26/40] sched, numa, mm: Count WS scanning against present PTEs, not virtual memory ranges Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 27/40] mm: sched: numa: Implement slow start for working set sampling Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 28/40] mm: numa: Add pte updates, hinting and migration stats Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 29/40] mm: numa: Migrate on reference policy Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 30/40] mm: numa: Migrate pages handled during a pmd_numa hinting fault Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 31/40] mm: numa: Structures for Migrate On Fault per NUMA migration rate limiting Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 32/40] mm: numa: Rate limit the amount of memory that is migrated between nodes Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 33/40] mm: numa: Rate limit setting of pte_numa if node is saturated Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 34/40] sched: numa: Slowly increase the scanning period as NUMA faults are handled Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 35/40] mm: numa: Introduce last_nid to the page frame Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 36/40] mm: numa: Use a two-stage filter to restrict pages being migrated for unlikely task<->node relationships Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 37/40] mm: numa: Add THP migration for the NUMA working set scanning fault case Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-23 10:43 ` [PATCH] mm: numa: Add THP migration for the NUMA working set scanning fault case -fixes Mel Gorman
2012-11-23 10:43 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 38/40] mm: sched: Adapt the scanning rate if a NUMA hinting fault does not migrate Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 39/40] mm: sched: numa: Control enabling and disabling of NUMA balancing Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-22 19:25 ` [PATCH 40/40] mm: sched: numa: Delay PTE scanning until a task is scheduled on a new node Mel Gorman
2012-11-22 19:25 ` Mel Gorman
2012-11-26 14:58 ` [PATCH 00/41] Automatic NUMA Balancing V6 Mel Gorman
2012-11-26 14:58 ` Mel Gorman
2012-11-28 13:49 ` [PATCH 00/45] Automatic NUMA Balancing V7 Mel Gorman
2012-11-28 13:49 ` Mel Gorman
2012-11-30 11:33 ` [PATCH 00/46] Automatic NUMA Balancing V8 Mel Gorman
2012-11-30 11:33 ` Mel Gorman
2012-11-30 11:41 ` Results for balancenuma v8, autonuma-v28fast and numacore-20121126 Mel Gorman
2012-11-30 11:41 ` Mel Gorman
2012-11-30 16:09 ` Rik van Riel
2012-11-30 16:09 ` Rik van Riel
2012-12-07 10:45 ` [PATCH 00/45] Automatic NUMA Balancing V7 Srikar Dronamraju
2012-12-07 10:45 ` Srikar Dronamraju
2012-12-10 9:07 ` Mel Gorman
2012-12-10 9:07 ` Mel Gorman
2012-12-10 9:42 ` Srikar Dronamraju [this message]
2012-12-10 9:42 ` Srikar Dronamraju
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=20121210094257.GB6348@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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.