From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by kanga.kvack.org (Postfix) with ESMTP id 10C116B0005 for ; Fri, 19 Feb 2016 10:43:56 -0500 (EST) Received: by mail-io0-f173.google.com with SMTP id g203so113177200iof.2 for ; Fri, 19 Feb 2016 07:43:56 -0800 (PST) Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net. [2001:558:fe21:29:69:252:207:35]) by mx.google.com with ESMTPS id v4si14165684igd.0.2016.02.19.07.43.55 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 19 Feb 2016 07:43:55 -0800 (PST) Date: Fri, 19 Feb 2016 09:43:54 -0600 (CST) From: Christoph Lameter Subject: Re: [PATCH v1 8/8] mm: kasan: Initial memory quarantine implementation In-Reply-To: Message-ID: References: <1cec06645310eeb495bcae7bed0807dbf2235f3a.1453918525.git.glider@google.com> <20160201024715.GC32125@js1304-P5Q-DELUXE> Content-Type: text/plain; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Dmitry Vyukov Cc: Joonsoo Kim , Alexander Potapenko , Joonsoo Kim , Andrey Konovalov , Andrew Morton , Andrey Ryabinin , Steven Rostedt , kasan-dev , LKML , Linux Memory Management List On Fri, 19 Feb 2016, Dmitry Vyukov wrote: > No, this does not work. We've tried. > The problem is fragmentation. When all memory is occupied by slab, > it's already too late to reclaim memory. Free objects are randomly > scattered over memory, so if you have just 1% of live objects, the > chances are that you won't be able to reclaim any single page. Yes that is why slab objects *need* to be *movable*!!! -- 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