From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with ESMTP id 287426B0106 for ; Sun, 20 Sep 2009 06:01:26 -0400 (EDT) Message-ID: <4AB5FD4D.3070005@kernel.org> Date: Sun, 20 Sep 2009 19:00:45 +0900 From: Tejun Heo MIME-Version: 1.0 Subject: Re: [PATCH 1/3] slqb: Do not use DEFINE_PER_CPU for per-node data References: <1253302451-27740-1-git-send-email-mel@csn.ul.ie> <1253302451-27740-2-git-send-email-mel@csn.ul.ie> <84144f020909200145w74037ab9vb66dae65d3b8a048@mail.gmail.com> In-Reply-To: <84144f020909200145w74037ab9vb66dae65d3b8a048@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Pekka Enberg Cc: Mel Gorman , Nick Piggin , Christoph Lameter , heiko.carstens@de.ibm.com, sachinp@in.ibm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton List-ID: Pekka Enberg wrote: > On Fri, Sep 18, 2009 at 10:34 PM, Mel Gorman wrote: >> SLQB used a seemingly nice hack to allocate per-node data for the statically >> initialised caches. Unfortunately, due to some unknown per-cpu >> optimisation, these regions are being reused by something else as the >> per-node data is getting randomly scrambled. This patch fixes the >> problem but it's not fully understood *why* it fixes the problem at the >> moment. > > Ouch, that sounds bad. I guess it's architecture specific bug as x86 > works ok? Lets CC Tejun. Is the corruption being seen on ppc or s390? Thanks. -- tejun -- 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: email@kvack.org