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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 04962C00454 for ; Tue, 10 Dec 2019 15:07:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D80EC2073B for ; Tue, 10 Dec 2019 15:07:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727528AbfLJPHm (ORCPT ); Tue, 10 Dec 2019 10:07:42 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:40009 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727272AbfLJPHm (ORCPT ); Tue, 10 Dec 2019 10:07:42 -0500 Received: by mail-ot1-f68.google.com with SMTP id i15so15772880oto.7; Tue, 10 Dec 2019 07:07:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gK9WhM7XsDaY+lb7/ANGcV/P86c0uO6eQPbXi7xswFE=; b=eIH4lr9LaBZSeOFhwlWBesw20u7HhJynzzXSFuID/eOnC6umFrgnqgfC26BH4hkwca HWxdcjAC/5PxldYp33FLiAMwANVdV8qrYnAgFWiN/M2sULha8b3XhJPL/pj2C/bndSbZ zI1p9AFepvSShSph8KDRHCDnbQNA8aNi9I7NhfKXs1RaN3w62DTAxQBuc1eiOizIVKA2 7wE5qFTCy1LFyzzDk04MWtUv5Xn7IJEweh4ZOKAcGUCP8GyZ0/JYqn9Q7Q05xLl1G/M1 cTCs/hWSyTde/n5Pk41XIKLrnmCCw5+5BWkkmVeir/03GbfQTHtIJP2GGFAJt/+NF6N0 3OHg== X-Gm-Message-State: APjAAAWwIx+eFRKUOyN5B9RlGPFOOPB8iCMCjDgn8g53ZaIpITc82rWD ARRU5segUdovbFVlI/XoShCL0XbGyJNGr79Rz7M= X-Google-Smtp-Source: APXvYqwC9TBYwf2pyNK0Qv54QJWthYsUOMkaDtrE0Tk9LHTcQq/Y/VTDQ4Y51lg891cIGW1OjaKmhctBQZh2r1ySNGc= X-Received: by 2002:a9d:7984:: with SMTP id h4mr21315284otm.297.1575990461076; Tue, 10 Dec 2019 07:07:41 -0800 (PST) MIME-Version: 1.0 References: <20191030184844.84219-1-edumazet@google.com> In-Reply-To: From: Geert Uytterhoeven Date: Tue, 10 Dec 2019 16:07:30 +0100 Message-ID: Subject: Re: [PATCH] dma-debug: increase HASH_SIZE To: Eric Dumazet Cc: Christoph Hellwig , linux-kernel , Eric Dumazet , Marek Szyprowski , Linux-Renesas 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 Hi Eric, On Tue, Dec 10, 2019 at 4:04 PM Eric Dumazet wrote: > On Tue, Dec 10, 2019 at 6:55 AM Geert Uytterhoeven wrote: > > JFTR, this increases dma_entry_hash size by 327680 bytes, and pushes > > a few more boards beyond their bootloader-imposed kernel size limits. > > > > Disabling CONFIG_DMA_API_DEBUG fixes that. > > Of course the real fix is to fix the bootloaders... > > Maybe we can make the hash size arch-dependent, or better dynamically > allocate this memory ? Dynamically allocating would be the better solution, IMHO. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds