From: Christoph Lameter <cl@linux.com>
To: Andrey Ryabinin <a.ryabinin@samsung.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Pekka Enberg <penberg@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Sasha Levin <sasha.levin@oracle.com>,
Dmitry Chernenkov <dmitryc@google.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] slub memory quarantine
Date: Tue, 3 Mar 2015 10:42:07 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.11.1503031041340.14643@gentwo.org> (raw)
In-Reply-To: <54F5D5CC.6070901@samsung.com>
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.
prev parent reply other threads:[~2015-03-03 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 8:55 Andrey Ryabinin
2015-03-03 9:10 ` Dmitry Vyukov
2015-03-03 15:39 ` Andrey Ryabinin
2015-03-03 16:42 ` Christoph Lameter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.11.1503031041340.14643@gentwo.org \
--to=cl@linux.com \
--cc=a.ryabinin@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=dmitryc@google.com \
--cc=dvyukov@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®