From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932278AbbCCQmM (ORCPT ); Tue, 3 Mar 2015 11:42:12 -0500 Received: from resqmta-ch2-08v.sys.comcast.net ([69.252.207.40]:39992 "EHLO resqmta-ch2-08v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755016AbbCCQmK (ORCPT ); Tue, 3 Mar 2015 11:42:10 -0500 Date: Tue, 3 Mar 2015 10:42:07 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Andrey Ryabinin cc: Dmitry Vyukov , Andrew Morton , David Rientjes , Joonsoo Kim , Pekka Enberg , Linux Memory Management List , Sasha Levin , Dmitry Chernenkov , Konstantin Khlebnikov , LKML Subject: Re: [RFC] slub memory quarantine In-Reply-To: <54F5D5CC.6070901@samsung.com> Message-ID: References: <54F57716.80809@samsung.com> <54F5D5CC.6070901@samsung.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 Tue, 3 Mar 2015, Andrey Ryabinin wrote: > On 03/03/2015 12:10 PM, Dmitry Vyukov wrote: > > Please hold on with this. > > Dmitry Chernenkov is working on a quarantine that works with both slub > > and slab, does not cause spurious OOMs and does not depend on > > slub-debug which has unacceptable performance (acquires global lock). > > I think that it's a separate issue. KASan already depend on slub_debug - it required for redzones/user tracking. > I think that some parts slub debugging (like user tracking and this quarantine) > could be moved (for CONFIG_KASAN=y) to the fast path without any locking. In general these features need to be ifdeffed out since they add significant overhead for the data structures and execution paths.