linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Nick Piggin <npiggin@suse.de>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	heiko.carstens@de.ibm.com, sachinp@in.ibm.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] slqb: Treat pages freed on a memoryless node as local node
Date: Fri, 18 Sep 2009 17:01:14 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0909181657280.9490@V090114053VZO-1> (raw)
In-Reply-To: <1253302451-27740-3-git-send-email-mel@csn.ul.ie>

On Fri, 18 Sep 2009, Mel Gorman wrote:

> --- a/mm/slqb.c
> +++ b/mm/slqb.c
> @@ -1726,6 +1726,7 @@ static __always_inline void __slab_free(struct kmem_cache *s,
>  	struct kmem_cache_cpu *c;
>  	struct kmem_cache_list *l;
>  	int thiscpu = smp_processor_id();
> +	int thisnode = numa_node_id();

thisnode must be the first reachable node with usable RAM. Not the current
node. cpu 0 may be on node 0 but there is no memory on 0. Instead
allocations fall back to node 2 (depends on policy effective as well. The
round robin meory policy default on bootup may result in allocations from
different nodes as well).

>  	c = get_cpu_slab(s, thiscpu);
>  	l = &c->list;
> @@ -1733,12 +1734,14 @@ static __always_inline void __slab_free(struct kmem_cache *s,
>  	slqb_stat_inc(l, FREE);
>
>  	if (!NUMA_BUILD || !slab_numa(s) ||
> -			likely(slqb_page_to_nid(page) == numa_node_id())) {
> +			likely(slqb_page_to_nid(page) == numa_node_id() ||
> +			!node_state(thisnode, N_HIGH_MEMORY))) {

Same here.

Note that page_to_nid can yield surprising results if you are trying to
allocate from a node that has no memory and you get some fallback node.

SLAB for some time had a bug that caused list corruption because of this.

--
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:[~2009-09-18 21:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 19:34 [RFC PATCH 0/3] Hatchet job for SLQB on memoryless configurations Mel Gorman
2009-09-18 19:34 ` [PATCH 1/3] slqb: Do not use DEFINE_PER_CPU for per-node data Mel Gorman
2009-09-20  8:45   ` Pekka Enberg
2009-09-20 10:00     ` Tejun Heo
2009-09-20 10:12       ` Pekka Enberg
2009-09-20 15:55         ` Tejun Heo
2009-09-21  6:24           ` Pekka Enberg
2009-09-21  8:46             ` Mel Gorman
2009-09-21  8:30           ` Sachin Sant
2009-09-21  8:42             ` Mel Gorman
2009-09-21  9:00               ` Tejun Heo
2009-09-21  9:44                 ` Mel Gorman
2009-09-21  9:53                   ` Tejun Heo
2009-09-21 10:04                     ` Mel Gorman
2009-09-21  9:02               ` Sachin Sant
2009-09-21  9:09                 ` Mel Gorman
2009-09-21 13:04               ` Mel Gorman
2009-09-21 13:31                 ` Pekka Enberg
2009-09-21 13:45                 ` Tejun Heo
2009-09-21 13:57                   ` Mel Gorman
2009-09-21 23:54                     ` Benjamin Herrenschmidt
2009-09-20 14:04     ` Mel Gorman
2009-09-18 19:34 ` [PATCH 2/3] slqb: Treat pages freed on a memoryless node as local node Mel Gorman
2009-09-18 21:01   ` Christoph Lameter [this message]
2009-09-19 11:46     ` Mel Gorman
2009-09-21 17:34       ` Lee Schermerhorn
2009-09-22 13:33         ` Mel Gorman
2009-09-22 18:29           ` Lee Schermerhorn
2009-09-18 19:34 ` [PATCH 3/3] slqb: Allow SLQB to be used on PPC and S390 Mel Gorman

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=alpine.DEB.1.10.0909181657280.9490@V090114053VZO-1 \
    --to=cl@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=sachinp@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox