Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756340Ab2FJK13 (ORCPT ); Sun, 10 Jun 2012 06:27:29 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:44117 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754754Ab2FJK11 (ORCPT ); Sun, 10 Jun 2012 06:27:27 -0400 MIME-Version: 1.0 In-Reply-To: References: <1339176197-13270-1-git-send-email-js1304@gmail.com> <1339176197-13270-4-git-send-email-js1304@gmail.com> Date: Sun, 10 Jun 2012 19:27:27 +0900 Message-ID: Subject: Re: [PATCH 4/4] slub: deactivate freelist of kmem_cache_cpu all at once in deactivate_slab() From: JoonSoo Kim To: Christoph Lameter Cc: Pekka Enberg , linux-kernel@vger.kernel.org, linux-mm@kvack.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1179 Lines: 27 2012/6/9 Christoph Lameter : > On Sat, 9 Jun 2012, Joonsoo Kim wrote: > >> Current implementation of deactivate_slab() which deactivate >> freelist of kmem_cache_cpu one by one is inefficient. >> This patch changes it to deactivate freelist all at once. >> But, there is no overall performance benefit, >> because deactivate_slab() is invoked infrequently. > > Hmm, deactivate freelist can race with slab_free. Need to look at this in > detail. Implemented logic is nearly same as previous one. I just merge first step of previous deactivate_slab() with second one. In case of failure of cmpxchg_double_slab(), reloading page->freelist, page->counters and recomputing inuse ensure that race with slab_free() cannot be possible. In case that we need a lock, try to get a lock before invoking cmpxchg_double_slab(), so race with slab_free cannot be occured too. Above is my humble opinion, please give me some comments. -- 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/