LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, netdev@vger.kernel.org,
linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] mm: kill kmemcheck
Date: Wed, 11 Mar 2015 10:43:29 -0400 [thread overview]
Message-ID: <55005491.5080809@oracle.com> (raw)
In-Reply-To: <20150311102636.6b4110a8@gandalf.local.home>
On 03/11/2015 10:26 AM, Steven Rostedt wrote:
>> There's no real hurry to kill kmemcheck right now, but we do want to stop
>> > supporting that in favour of KASan.
> Understood, but the kernel is suppose to support older compilers.
> Perhaps we can keep kmemcheck for now and say it's obsoleted if you
> have a newer compiler. Because it will be a while before I upgrade my
> compilers. I don't upgrade unless I have a good reason to do so. Not
> sure KASan fulfills that requirement.
It's not that there's a performance overhead with kmemcheck, it's the
maintenance effort that we want to get rid of.
The kernel should keep supporting old kernels, and after this kmemcheck
removal your kernel will still keep working - this is more of a removal
of a mostly unused feature that had hooks everywhere in the kernel.
Did you actually find anything recently with kmemcheck? How do you deal
with the 1 CPU limit and the massive performance hit?
Could you try KASan for your use case and see if it potentially uncovers
anything new?
Thanks,
Sasha
next prev parent reply other threads:[~2015-03-11 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1426074547-21888-1-git-send-email-sasha.levin@oracle.com>
2015-03-11 12:19 ` Steven Rostedt
2015-03-11 12:34 ` Sasha Levin
2015-03-11 12:40 ` Steven Rostedt
2015-03-11 13:39 ` Sasha Levin
2015-03-11 14:23 ` Dave Jones
2015-03-11 14:26 ` Steven Rostedt
2015-03-11 14:43 ` Sasha Levin [this message]
2015-03-11 14:52 ` Steven Rostedt
2015-03-17 1:48 ` Sasha Levin
2015-03-17 2:33 ` Steven Rostedt
2015-03-11 14:35 ` Boaz Harrosh
2015-03-11 17:20 ` David Miller
2015-03-11 17:25 ` Sasha Levin
2015-03-11 18:44 ` David Miller
2015-03-11 20:01 ` Andrey Ryabinin
2015-03-11 20:48 ` David Miller
[not found] ` <1426132192.25936.7.camel@ellerman.id.au>
[not found] ` <55018936.5080805@oracle.com>
2015-03-12 18:11 ` David Miller
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=55005491.5080809@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--subject='Re: [PATCH] mm: kill kmemcheck' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).