From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, T_DKIMWL_WL_MED,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 02011C43141 for ; Thu, 28 Jun 2018 18:29:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B037523EAB for ; Thu, 28 Jun 2018 18:29:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="JSZ1csOr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B037523EAB Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030480AbeF1S3N (ORCPT ); Thu, 28 Jun 2018 14:29:13 -0400 Received: from mail-it0-f67.google.com ([209.85.214.67]:35874 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966642AbeF1S3J (ORCPT ); Thu, 28 Jun 2018 14:29:09 -0400 Received: by mail-it0-f67.google.com with SMTP id j135-v6so13971668itj.1 for ; Thu, 28 Jun 2018 11:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TQhutihisTXpuVK+GeZtz9M18UfcHNomSTyGrQh5D3k=; b=JSZ1csOr3Sm14ZQDqMhEU2FZtPA0izBLiOxP7kTlJIKJBlUSOqsi4bUtHeSOnY7Lej K09YeARZuPuy6SF5GiBwk6X1toDdp3b3YB2rixnh8+86UceBRZ5kgzoHDFsITEvgvGd/ uahw5P2T69SZ5kfCbr12maADD5tCS/ZEAR8GHZFfuQKA6qgRDyuQiWxpUUJnSBj5agOe zLqTgtTOMjFEi2MuyJE208a+0Jkk+YUxpOaZFyEB17FoYJjbcEjBviVkQBO0WcTnFBbz GD9E+NkwvHmcxRLNTnVB5RbHpaDmR2eMFggQYznfD12PRgxvJnr+9yj8tlOYLUCkpZKa qTYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TQhutihisTXpuVK+GeZtz9M18UfcHNomSTyGrQh5D3k=; b=kG9T4crDHyEgt5jxG9XSQ35BO6K4mKwx18CBqQQSD50+coAJMj4D1ny9C7Rur3uNLq TmSNKpatHCcVFZXu8AuhB/TaeQqigFSdeImSpGNSADfkFs8zXdmk42CwLFJmrDcusok+ TCRz0Hxz/COSOO6uINAEVkC9TxbBXBGSVnbCC8Hp8YubzTuM4tBqfkgpP65iM6Db9C85 ZuviwLRWHBsKGl+l1rQU73pYcV0KzlCJCjY0xipLdQUvlaiD9QULuEwpa+4a4YVXqfIL b62dB9zsMgv7K5kFa0ZeaUwbPFFP+PgTV/H15OEVJ9FAHBE+K543SuVtC8HNAscFjzqi AmtA== X-Gm-Message-State: APt69E0mBEhKLB2wPtfkpv1ldZY4yYVRvuvxrYKIXUPyPJ765qAAp5Xk VVT85xaKjg081WcQUC2wwvtHzB18wR17SuEOPBXTzw== X-Google-Smtp-Source: AAOMgpdfCxEmrXGN9cYPDwN3cYkZXTvqm5ONB3XHlhMsbqBrB38enIQPq9jbMYnsmumlsBlFJR0maFDxu1GlsCUtjOY= X-Received: by 2002:a24:ca43:: with SMTP id k64-v6mr10130862itg.44.1530210548456; Thu, 28 Jun 2018 11:29:08 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:9082:0:0:0:0:0 with HTTP; Thu, 28 Jun 2018 11:29:07 -0700 (PDT) In-Reply-To: <20180627160800.3dc7f9ee41c0badbf7342520@linux-foundation.org> References: <20180627160800.3dc7f9ee41c0badbf7342520@linux-foundation.org> From: Andrey Konovalov Date: Thu, 28 Jun 2018 20:29:07 +0200 Message-ID: Subject: Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address sanitizer To: Andrew Morton Cc: Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Catalin Marinas , Will Deacon , Christoph Lameter , Mark Rutland , Nick Desaulniers , Marc Zyngier , Dave Martin , Ard Biesheuvel , "Eric W . Biederman" , Ingo Molnar , Paul Lawrence , Geert Uytterhoeven , Arnd Bergmann , "Kirill A . Shutemov" , Greg Kroah-Hartman , Kate Stewart , Mike Rapoport , kasan-dev , linux-doc@vger.kernel.org, LKML , Linux ARM , linux-sparse@vger.kernel.org, Linux Memory Management List , Linux Kbuild mailing list , Kostya Serebryany , Evgeniy Stepanov , Lee Smith , Ramana Radhakrishnan , Jacob Bramley , Ruben Ayrapetyan , Jann Horn , Mark Brand , Chintan Pandya Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 28, 2018 at 1:08 AM, Andrew Morton wrote: > On Tue, 26 Jun 2018 15:15:10 +0200 Andrey Konovalov wrote: >> ====== Benchmarks >> >> The following numbers were collected on Odroid C2 board. Both KASAN and >> KHWASAN were used in inline instrumentation mode. >> >> Boot time [1]: >> * ~1.7 sec for clean kernel >> * ~5.0 sec for KASAN >> * ~5.0 sec for KHWASAN >> >> Slab memory usage after boot [2]: >> * ~40 kb for clean kernel >> * ~105 kb + 1/8th shadow ~= 118 kb for KASAN >> * ~47 kb + 1/16th shadow ~= 50 kb for KHWASAN >> >> Network performance [3]: >> * 8.33 Gbits/sec for clean kernel >> * 3.17 Gbits/sec for KASAN >> * 2.85 Gbits/sec for KHWASAN >> >> Note, that KHWASAN (compared to KASAN) doesn't require quarantine. >> >> [1] Time before the ext4 driver is initialized. >> [2] Measured as `cat /proc/meminfo | grep Slab`. >> [3] Measured as `iperf -s & iperf -c 127.0.0.1 -t 30`. > > The above doesn't actually demonstrate the whole point of the > patchset: to reduce KASAN's very high memory consumption? You mean that memory usage numbers collected after boot don't give a representative picture of actual memory consumption on real workloads? What kind of memory consumption testing would you like to see?