From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755008AbZA1QoO (ORCPT ); Wed, 28 Jan 2009 11:44:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751790AbZA1Qn6 (ORCPT ); Wed, 28 Jan 2009 11:43:58 -0500 Received: from smtp3.ultrahosting.com ([74.213.175.254]:39961 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751603AbZA1Qn5 (ORCPT ); Wed, 28 Jan 2009 11:43:57 -0500 Date: Wed, 28 Jan 2009 11:40:14 -0500 (EST) From: Christoph Lameter X-X-Sender: cl@qirst.com To: Pekka Enberg cc: David Rientjes , linux-kernel@vger.kernel.org Subject: Re: [patch] slub: fix per cpu kmem_cache_cpu array memory leak In-Reply-To: <1233134864.16201.3.camel@penberg-laptop> Message-ID: References: <1233132733.16201.0.camel@penberg-laptop> <84144f020901280058h36fedf37j600185c255db5e2a@mail.gmail.com> <1233134864.16201.3.camel@penberg-laptop> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Jan 2009, Pekka Enberg wrote: > The bug has been there for a very long time and hasn't generated any bug > reports so I think I'll just push it to mainline and leave it that. Typically we do not run out of elements of the per cpu array. Note that this code can be removed if we finally get a per cpu allocator.