All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <aarcange@redhat.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Rik van Riel <riel@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, Paul Turner <pjt@google.com>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	Christoph Lameter <cl@linux.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Benchmark results: "Enhanced NUMA scheduling with adaptive affinity"
Date: Fri, 16 Nov 2012 20:50:18 +0100	[thread overview]
Message-ID: <20121116195018.GA8908@redhat.com> (raw)
In-Reply-To: <20121116141428.GZ8218@suse.de>

Hi,

On Fri, Nov 16, 2012 at 02:14:28PM +0000, Mel Gorman wrote:
> With some shuffling the question on what to consider for merging
> becomes
> 
>
> 1. TLB optimisation patches 1-3?	 	Patches  1-3

I assume you mean simply reshuffling 33-35 as 1-3.

> 2. Stats for migration?				Patches  4-6
> 3. Common NUMA infrastructure?			Patches  7-21
> 4. Basic fault-driven policy, stats, ratelimits	Patches 22-35
> 
> Patches 36-43 are complete cabbage and should not be considered at this
> stage. It should be possible to build the placement policies and the
> scheduling decisions from schednuma, autonuma, some combination of the
> above or something completely different on top of patches 1-35.
> 
> Peter, Ingo, Andrea?

The patches 1-35 looks a great foundation so I think they'd be an
ideal candidate for a first upstream inclusion.

Thanks,
Andrea

--
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: Andrea Arcangeli <aarcange@redhat.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Rik van Riel <riel@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, Paul Turner <pjt@google.com>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	Christoph Lameter <cl@linux.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Benchmark results: "Enhanced NUMA scheduling with adaptive affinity"
Date: Fri, 16 Nov 2012 20:50:18 +0100	[thread overview]
Message-ID: <20121116195018.GA8908@redhat.com> (raw)
In-Reply-To: <20121116141428.GZ8218@suse.de>

Hi,

On Fri, Nov 16, 2012 at 02:14:28PM +0000, Mel Gorman wrote:
> With some shuffling the question on what to consider for merging
> becomes
> 
>
> 1. TLB optimisation patches 1-3?	 	Patches  1-3

I assume you mean simply reshuffling 33-35 as 1-3.

> 2. Stats for migration?				Patches  4-6
> 3. Common NUMA infrastructure?			Patches  7-21
> 4. Basic fault-driven policy, stats, ratelimits	Patches 22-35
> 
> Patches 36-43 are complete cabbage and should not be considered at this
> stage. It should be possible to build the placement policies and the
> scheduling decisions from schednuma, autonuma, some combination of the
> above or something completely different on top of patches 1-35.
> 
> Peter, Ingo, Andrea?

The patches 1-35 looks a great foundation so I think they'd be an
ideal candidate for a first upstream inclusion.

Thanks,
Andrea

  reply	other threads:[~2012-11-16 19:50 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 16:04 [PATCH 0/8] Announcement: Enhanced NUMA scheduling with adaptive affinity Peter Zijlstra
2012-11-12 16:04 ` Peter Zijlstra
2012-11-12 16:04 ` [PATCH 1/8] sched, numa, mm: Introduce sched_feat_numa() Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-12 16:04 ` [PATCH 2/8] sched, numa, mm: Implement THP migration Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-12 16:04 ` [PATCH 3/8] sched, numa, mm: Add credits for NUMA placement Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-12 16:04 ` [PATCH 4/8] sched, numa, mm: Add last_cpu to page flags Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-13 11:55   ` Ingo Molnar
2012-11-13 11:55     ` Ingo Molnar
2012-11-13 16:09   ` Rik van Riel
2012-11-13 16:09     ` Rik van Riel
2012-11-12 16:04 ` [PATCH 5/8] sched, numa, mm: Add adaptive NUMA affinity support Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-13  0:02   ` Christoph Lameter
2012-11-13  0:02     ` Christoph Lameter
2012-11-13  8:19     ` Ingo Molnar
2012-11-13  8:19       ` Ingo Molnar
2012-11-13 22:57   ` Rik van Riel
2012-11-13 22:57     ` Rik van Riel
2012-11-16 18:06   ` Rik van Riel
2012-11-16 18:06     ` Rik van Riel
2012-11-16 18:14     ` Ingo Molnar
2012-11-16 18:14       ` Ingo Molnar
2012-11-16 18:23       ` Rik van Riel
2012-11-16 18:23         ` Rik van Riel
2012-11-29 19:34   ` Andi Kleen
2012-11-29 19:34     ` Andi Kleen
2012-11-12 16:04 ` [PATCH 6/8] sched, numa, mm: Implement constant, per task Working Set Sampling (WSS) rate Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-12 16:04 ` [PATCH 7/8] sched, numa, mm: Count WS scanning against present PTEs, not virtual memory ranges Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-12 16:04 ` [PATCH 8/8] sched, numa, mm: Implement slow start for working set sampling Peter Zijlstra
2012-11-12 16:04   ` Peter Zijlstra
2012-11-12 18:48 ` Benchmark results: "Enhanced NUMA scheduling with adaptive affinity" Ingo Molnar
2012-11-12 18:48   ` Ingo Molnar
2012-11-15 10:08   ` Mel Gorman
2012-11-15 10:08     ` Mel Gorman
2012-11-15 18:52     ` Rik van Riel
2012-11-15 18:52       ` Rik van Riel
2012-11-15 21:27       ` Mel Gorman
2012-11-15 21:27         ` Mel Gorman
2012-11-15 20:32     ` Linus Torvalds
2012-11-15 20:32       ` Linus Torvalds
2012-11-15 22:04       ` Rik van Riel
2012-11-15 22:04         ` Rik van Riel
2012-11-16 14:14         ` Mel Gorman
2012-11-16 14:14           ` Mel Gorman
2012-11-16 19:50           ` Andrea Arcangeli [this message]
2012-11-16 19:50             ` Andrea Arcangeli
2012-11-16 20:05             ` Mel Gorman
2012-11-16 20:05               ` Mel Gorman
2012-11-16 16:16       ` Ingo Molnar
2012-11-16 16:16         ` Ingo Molnar
2012-11-16 15:56     ` Ingo Molnar
2012-11-16 15:56       ` Ingo Molnar
2012-11-16 16:25       ` Mel Gorman
2012-11-16 16:25         ` Mel Gorman
2012-11-16 17:49         ` Ingo Molnar
2012-11-16 17:49           ` Ingo Molnar
2012-11-16 19:04           ` Mel Gorman
2012-11-16 19:04             ` Mel Gorman
2012-11-12 23:43 ` [PATCH 0/8] Announcement: Enhanced NUMA scheduling with adaptive affinity Christoph Lameter
2012-11-12 23:43   ` Christoph Lameter
2012-11-13  7:24   ` Ingo Molnar
2012-11-13  7:24     ` Ingo Molnar
2012-11-15 14:26     ` Christoph Lameter
2012-11-15 14:26       ` Christoph Lameter
2012-11-16 15:59       ` Ingo Molnar
2012-11-16 15:59         ` Ingo Molnar
2012-11-16 20:57         ` Christoph Lameter
2012-11-16 20:57           ` Christoph Lameter

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=20121116195018.GA8908@redhat.com \
    --to=aarcange@redhat.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=pjt@google.com \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --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.