From: Takashi Iwai <tiwai@suse.de>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: broonie@kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: Fix fragmentation regression in firmware download
Date: Wed, 04 Mar 2026 16:17:54 +0100 [thread overview]
Message-ID: <87fr6fvd25.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260304141250.1578597-1-rf@opensource.cirrus.com>
On Wed, 04 Mar 2026 15:12:50 +0100,
Richard Fitzgerald wrote:
>
> Use vmalloc() instead of kmalloc(..., GFP_DMA) to alloc the temporary
> buffer for firmware download blobs. This avoids the problem that a
> heavily fragmented system cannot allocate enough physically-contiguous
> memory for a large blob.
>
> The redundant alloc buffer mechanism was removed in commit 900baa6e7bb0
> ("firmware: cs_dsp: Remove redundant download buffer allocator").
> While doing that I was overly focused on the possibility of the
> underlying bus requiring DMA-safe memory. So I used GFP_DMA kmalloc()s.
> I failed to notice that the code I was removing used vmalloc().
> This creates a regression.
>
> Way back in 2014 the problem of fragmentation with kmalloc()s was fixed
> by commit cdcd7f728753 ("ASoC: wm_adsp: Use vmalloc to allocate firmware
> download buffer").
>
> Although we don't need physically-contiguous memory, we don't know if the
> bus needs some particular alignment of the buffers. Since the change in
> 2014, the firmware download has always used whatever alignment vmalloc()
> returns. To avoid introducing a new problem, the temporary buffer is still
> used, to keep the same alignment of pointers passed to regmap_raw_write().
>
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> Fixes: 900baa6e7bb0 ("firmware: cs_dsp: Remove redundant download buffer allocator")
FYI, if the data isn't always large, kvmalloc() could be a better
alternative, which is a hybrid for both speed and size, too.
Takashi
next prev parent reply other threads:[~2026-03-04 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 14:12 [PATCH] firmware: cs_dsp: Fix fragmentation regression in firmware download Richard Fitzgerald
2026-03-04 15:17 ` Takashi Iwai [this message]
2026-03-04 15:35 ` Richard Fitzgerald
2026-03-04 16:12 ` Takashi Iwai
2026-03-09 15:12 ` Mark Brown
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=87fr6fvd25.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox