On 11/21/2014 02:00 AM, Andrew Morton wrote: > On Thu, 20 Nov 2014 20:32:30 +0400 Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > >> Let me provide some background first. > > Well that was useful. Andrey, please slurp Dmitry's info into the 0/n > changelog? > Sure. > Also, some quantitative info about the kmemleak overhead would be > useful. > Confused. Perhaps you mean kmemcheck? I did some brief performance testing: $ netperf -l 30 MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to localhost (127.0.0.1) port 0 AF_INET Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec no debug: 87380 16384 16384 30.00 41624.72 kasan inline: 87380 16384 16384 30.00 12870.54 kasan outline: 87380 16384 16384 30.00 10586.39 kmemcheck: 87380 16384 16384 30.03 20.23 So on this workload kasan x500-x600 times faster then kmemcheck. > In this discussion you've mentioned a few planned kasan enhancements. > Please also list those and attempt to describe the amount of effort and > complexity levels. Partly so other can understand the plans and partly > so we can see what we're semi-committing ourselves to if we merge this > stuff. > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>