From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752672AbaBNSrZ (ORCPT ); Fri, 14 Feb 2014 13:47:25 -0500 Received: from qmta12.emeryville.ca.mail.comcast.net ([76.96.27.227]:38424 "EHLO qmta12.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751598AbaBNSrX (ORCPT ); Fri, 14 Feb 2014 13:47:23 -0500 Date: Fri, 14 Feb 2014 12:47:21 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@nuc To: Joonsoo Kim cc: Pekka Enberg , Andrew Morton , David Rientjes , Wanpeng Li , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Joonsoo Kim Subject: Re: [PATCH 7/9] slab: use the lock on alien_cache, instead of the lock on array_cache In-Reply-To: <1392361043-22420-8-git-send-email-iamjoonsoo.kim@lge.com> Message-ID: References: <1392361043-22420-1-git-send-email-iamjoonsoo.kim@lge.com> <1392361043-22420-8-git-send-email-iamjoonsoo.kim@lge.com> 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 Fri, 14 Feb 2014, Joonsoo Kim wrote: > Now, we have separate alien_cache structure, so it'd be better to hold > the lock on alien_cache while manipulating alien_cache. After that, > we don't need the lock on array_cache, so remove it. Acked-by: Christoph Lameter From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by kanga.kvack.org (Postfix) with ESMTP id 5D2B66B0035 for ; Fri, 14 Feb 2014 13:47:24 -0500 (EST) Received: by mail-qa0-f44.google.com with SMTP id w5so18579768qac.17 for ; Fri, 14 Feb 2014 10:47:24 -0800 (PST) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net. [2001:558:fe2d:43:76:96:30:16]) by mx.google.com with ESMTP id 108si4462745qgr.184.2014.02.14.10.47.23 for ; Fri, 14 Feb 2014 10:47:23 -0800 (PST) Date: Fri, 14 Feb 2014 12:47:21 -0600 (CST) From: Christoph Lameter Subject: Re: [PATCH 7/9] slab: use the lock on alien_cache, instead of the lock on array_cache In-Reply-To: <1392361043-22420-8-git-send-email-iamjoonsoo.kim@lge.com> Message-ID: References: <1392361043-22420-1-git-send-email-iamjoonsoo.kim@lge.com> <1392361043-22420-8-git-send-email-iamjoonsoo.kim@lge.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Joonsoo Kim Cc: Pekka Enberg , Andrew Morton , David Rientjes , Wanpeng Li , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Joonsoo Kim On Fri, 14 Feb 2014, Joonsoo Kim wrote: > Now, we have separate alien_cache structure, so it'd be better to hold > the lock on alien_cache while manipulating alien_cache. After that, > we don't need the lock on array_cache, so remove it. Acked-by: Christoph Lameter -- 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