[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdU2i8XABic0gUbSdCyBW=D3Rm+K+HR5DzUbxm8SpP-rHw@mail.gmail.com>
Date: Tue, 10 Dec 2019 16:07:30 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Christoph Hellwig <hch@....de>,
linux-kernel <linux-kernel@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH] dma-debug: increase HASH_SIZE
Hi Eric,
On Tue, Dec 10, 2019 at 4:04 PM Eric Dumazet <edumazet@...gle.com> wrote:
> On Tue, Dec 10, 2019 at 6:55 AM Geert Uytterhoeven <geert@...ux-m68k.org> 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@...ux-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
Powered by blists - more mailing lists