Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757132Ab1CXTEN (ORCPT ); Thu, 24 Mar 2011 15:04:13 -0400 Received: from mail-gx0-f174.google.com ([209.85.161.174]:59760 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757038Ab1CXTEM convert rfc822-to-8bit (ORCPT ); Thu, 24 Mar 2011 15:04:12 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=TdnHC8hJFGHc5eysK9nE6E12DKSQtvyTrdlXjBlZaR7csD59+nysmuMyFujpOfQWHy jbab5Nx0bC16OgmyoYd+ZfY4rSdgeCYzFZWmF18+26EkVoIZ7cFmJ6b3hcWDC06MtkU8 AF+DRVJEr1LwN5p8PHuQDHrj/jQqQi0zcricM= MIME-Version: 1.0 In-Reply-To: References: <20110324142146.GA11682@elte.hu> <20110324172653.GA28507@elte.hu> <1300990853.3747.189.camel@edumazet-laptop> <1300992708.3747.211.camel@edumazet-laptop> Date: Thu, 24 Mar 2011 21:04:11 +0200 X-Google-Sender-Auth: w_b_AmJNC0S7C4Tgde1dNr5clSk Message-ID: Subject: Re: [GIT PULL] SLAB changes for v2.6.39-rc1 From: Pekka Enberg To: Christoph Lameter Cc: Eric Dumazet , Ingo Molnar , torvalds@linux-foundation.org, akpm@linux-foundation.org, tj@kernel.org, npiggin@kernel.dk, rientjes@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 855 Lines: 25 On Thu, Mar 24, 2011 at 9:02 PM, Christoph Lameter wrote: > On Thu, 24 Mar 2011, Eric Dumazet wrote: > >> Le jeudi 24 mars 2011 ? 13:47 -0500, Christoph Lameter a ?crit : >> >> > Hmmm.. Could be. KVM would not really disable interrupts so this may >> > explain that the test case works here. >> > >> > Simple fix would be to do a load before the cli I guess. >> > >> >> Hmm... >> >> If we have a preemption and migration right after this load... > > Cannot be the issue here since init_kmem_cache_cpus already > touches the per cpu data. At least if CONFIG_PREEMPT is on. > Is it on? It's not. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/