From: Andrey Ryabinin <a.ryabinin@samsung.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
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, 03 Mar 2015 18:39:56 +0300 [thread overview]
Message-ID: <54F5D5CC.6070901@samsung.com> (raw)
In-Reply-To: <CACT4Y+YQ3cuUvRrT_19RbxFVWHGnzviSFi0-ud88jq9g9jUZog@mail.gmail.com>
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.
> Me or Dmitry C will send an email to kasan-dev@googlegroups.com to
> discuss quarantine development direction.
>
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-03-03 15:40 UTC|newest]
Thread overview: 5+ 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 [this message]
2015-03-03 16:42 ` Christoph Lameter
2015-03-03 17:36 ` Dmitry Chernenkov
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=54F5D5CC.6070901@samsung.com \
--to=a.ryabinin@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--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