All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Matt Mackall <mpm@selenic.com>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slob: poor man's NUMA support.
Date: Mon, 25 Jun 2007 16:17:56 +1000	[thread overview]
Message-ID: <467F5E14.5030401@yahoo.com.au> (raw)
In-Reply-To: <20070619090616.GA23697@linux-sh.org>

Paul Mundt wrote:
> This adds preliminary NUMA support to SLOB, primarily aimed at systems
> with small nodes (tested all the way down to a 128kB SRAM block), whether
> asymmetric or otherwise.

Fine by me as well, FWIW. My points about per-cpu/node queues were not
to say that I'm really opposed to getting this in first. In a way, you
sell yourself short with the patch name: the implementation may be just
a basic one, but simplicity is a key point of SLOB... Adding numa
awareness to the slob APIs is obviously a key step and makes it much
easier to experiment with enhancements to the implementation.

Unless it has been picked up already, I'd call it "initial NUMA support"
;) Thanks! Would be great to hear about your experiences using SLOB as
well -- how much memory you're saving, how it performs, etc.

-- 
SUSE Labs, Novell Inc.

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Matt Mackall <mpm@selenic.com>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slob: poor man's NUMA support.
Date: Mon, 25 Jun 2007 16:17:56 +1000	[thread overview]
Message-ID: <467F5E14.5030401@yahoo.com.au> (raw)
In-Reply-To: <20070619090616.GA23697@linux-sh.org>

Paul Mundt wrote:
> This adds preliminary NUMA support to SLOB, primarily aimed at systems
> with small nodes (tested all the way down to a 128kB SRAM block), whether
> asymmetric or otherwise.

Fine by me as well, FWIW. My points about per-cpu/node queues were not
to say that I'm really opposed to getting this in first. In a way, you
sell yourself short with the patch name: the implementation may be just
a basic one, but simplicity is a key point of SLOB... Adding numa
awareness to the slob APIs is obviously a key step and makes it much
easier to experiment with enhancements to the implementation.

Unless it has been picked up already, I'd call it "initial NUMA support"
;) Thanks! Would be great to hear about your experiences using SLOB as
well -- how much memory you're saving, how it performs, etc.

-- 
SUSE Labs, Novell Inc.

--
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>

  reply	other threads:[~2007-06-25  6:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19  9:06 [PATCH] slob: poor man's NUMA support Paul Mundt
2007-06-19  9:06 ` Paul Mundt
2007-06-25  6:17 ` Nick Piggin [this message]
2007-06-25  6:17   ` Nick Piggin
2007-06-25  6:20   ` Matt Mackall
2007-06-25  6:20     ` Matt Mackall
2007-06-26  7:21 ` Andrew Morton
2007-06-26  7:21   ` Andrew Morton
2007-06-26 18:14   ` Christoph Lameter
2007-06-26 18:14     ` Christoph Lameter
2007-06-26 19:04     ` Nish Aravamudan
2007-06-26 19:04       ` Nish Aravamudan
2007-06-26 19:10       ` Christoph Lameter
2007-06-26 19:10         ` Christoph Lameter
2007-06-26 19:17         ` Nish Aravamudan
2007-06-26 19:17           ` Nish Aravamudan
2007-06-26 19:20           ` Christoph Lameter
2007-06-26 19:20             ` 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=467F5E14.5030401@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    /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.